Displaying a scrollable list of affordances associated with physical activities

ABSTRACT

The present disclosure generally relates to managing user interfaces associated with physical activities. The user interface displays a scrollable list of affordances associated with physical activities. The affordances may contain physical activity and heart rate information. A user can launch a physical activity tracking function or an interface to change a workout metric using an affordance. Users can also control the music that is played in response to selecting a workout. Further, the interface can be used to compose a reply message to a received message that contains workout information. The interfaces can show a graph that includes heart data when the user&#39;s heart rate meets a heart rate alert criteria.

This application is a continuation of U.S. patent application Ser. No.15/705,849, entitled “DISPLAYING A SCROLLABLE LIST OF AFFORDANCESASSOCIATED WITH PHYSICAL ACTIVITIES”, filed Sep. 15, 2017, which claimspriority to U.S. Provisional Patent Application No. 62/506,304, entitled“DISPLAYING A SCROLLABLE LIST OF AFFORDANCES ASSOCIATED WITH PHYSICALACTIVITIES”, filed on May 15, 2017, the content of which are herebyincorporated by reference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces andmore specifically to techniques for displaying affordances associatedwith a physical activity.

BACKGROUND

Many modern electronic devices provide the capability of controlling aworkout tracking function. Some techniques for controlling a workouttracking function require multiple user inputs. These techniques can becumbersome and inefficient.

BRIEF SUMMARY

Some techniques for displaying affordances associated with a physicalactivity using electronic devices, however, are generally cumbersome andinefficient. For example, some existing techniques use a complex andtime-consuming user interface, which may include multiple key presses orkeystrokes. Existing techniques require more time than necessary,wasting user time and device energy. This latter consideration isparticularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for displaying affordancesassociated with a physical activity. Such methods and interfacesoptionally complement or replace other methods for displayingaffordances associated with a physical activity. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

In some embodiments, a method, comprising: at an electronic device witha display, a touch-sensitive surface, and a physical activity trackingsensor: displaying a scrollable list of affordances associated withphysical activities; displaying a first change workout metricsaffordance corresponding to a first affordance of the scrollable list ofaffordances; receiving a user input; in accordance with a determinationthat the user input is detected at the first affordance in thescrollable list of affordances, launching a physical activity trackingfunction associated with the selected first affordance; and inaccordance with a determination that the user input is detected at thefirst change workout metrics affordance, displaying a user interfaceconfigured to change a workout metric.

In some embodiments, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, a touch-sensitivesurface, and a physical activity tracking sensor, the one or moreprograms including instructions for: displaying a scrollable list ofaffordances associated with physical activities; displaying a firstchange workout metrics affordance corresponding to a first affordance ofthe scrollable list of affordances; receiving a user input; inaccordance with a determination that the user input is detected at thefirst affordance in the scrollable list of affordances, launching aphysical activity tracking function associated with the selected firstaffordance; and in accordance with a determination that the user inputis detected at the first change workout metrics affordance, displaying auser interface configured to change a workout metric.

In some embodiments, a transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, a touch-sensitivesurface, and a physical activity tracking sensor, the one or moreprograms including instructions for: displaying a scrollable list ofaffordances associated with physical activities; displaying a firstchange workout metrics affordance corresponding to a first affordance ofthe scrollable list of affordances; receiving a user input; inaccordance with a determination that the user input is detected at thefirst affordance in the scrollable list of affordances, launching aphysical activity tracking function associated with the selected firstaffordance; and in accordance with a determination that the user inputis detected at the first change workout metrics affordance, displaying auser interface configured to change a workout metric.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; a physical activity tracking sensor; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: displaying a scrollable list of affordancesassociated with physical activities; displaying a first change workoutmetrics affordance corresponding to a first affordance of the scrollablelist of affordances; receiving a user input; in accordance with adetermination that the user input is detected at the first affordance inthe scrollable list of affordances, launching a physical activitytracking function associated with the selected first affordance; and inaccordance with a determination that the user input is detected at thefirst change workout metrics affordance, displaying a user interfaceconfigured to change a workout metric.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; a physical activity tracking sensor; means fordisplaying a scrollable list of affordances associated with physicalactivities; means for displaying a first change workout metricsaffordance corresponding to a first affordance of the scrollable list ofaffordances; means for receiving a user input; means for in accordancewith a determination that the user input is detected at the firstaffordance in the scrollable list of affordances, launching a physicalactivity tracking function associated with the selected firstaffordance; and means for in accordance with a determination that theuser input is detected at the first change workout metrics affordance,displaying a user interface configured to change a workout metric.

In some embodiments, a method, comprising: at an electronic device witha display and a touch-sensitive surface: while an audio application isplaying audio content, displaying a scrollable list of affordancesassociated with physical activities; while the audio application isplaying the audio content, receiving a user input at an affordance ofthe scrollable list of affordances; and in response to receiving theuser input at the affordance: launching a physical activity trackingfunction associated with the selected affordance, and determiningwhether a workout audio playlist setting is enabled; in accordance witha determination that the workout audio playlist setting is enabled: stopplaying the audio content on the device, and initiate playing a workoutaudio playlist on the device; and in accordance with a determinationthat the workout audio playlist setting is disabled, continue playingthe audio content on the device.

In some embodiments, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display and a touch-sensitivesurface, the one or more programs including instructions for: while anaudio application is playing audio content, displaying a scrollable listof affordances associated with physical activities; while the audioapplication is playing the audio content, receiving a user input at anaffordance of the scrollable list of affordances; and in response toreceiving the user input at the affordance: launching a physicalactivity tracking function associated with the selected affordance, anddetermining whether a workout audio playlist setting is enabled; inaccordance with a determination that the workout audio playlist settingis enabled: stop playing the audio content on the device, and initiateplaying a workout audio playlist on the device; and in accordance with adetermination that the workout audio playlist setting is disabled,continue playing the audio content on the device.

In some embodiments, a transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display and a touch-sensitivesurface, the one or more programs including instructions for: while anaudio application is playing audio content, displaying a scrollable listof affordances associated with physical activities; while the audioapplication is playing the audio content, receiving a user input at anaffordance of the scrollable list of affordances; and in response toreceiving the user input at the affordance: launching a physicalactivity tracking function associated with the selected affordance, anddetermining whether a workout audio playlist setting is enabled; inaccordance with a determination that the workout audio playlist settingis enabled: stop playing the audio content on the device, and initiateplaying a workout audio playlist on the device; and in accordance with adetermination that the workout audio playlist setting is disabled,continue playing the audio content on the device.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; one or more processors; and memory storing oneor more programs configured to be executed by the one or moreprocessors, the one or more programs including instructions for: whilean audio application is playing audio content, displaying a scrollablelist of affordances associated with physical activities; while the audioapplication is playing the audio content, receiving a user input at anaffordance of the scrollable list of affordances; and in response toreceiving the user input at the affordance: launching a physicalactivity tracking function associated with the selected affordance, anddetermining whether a workout audio playlist setting is enabled; inaccordance with a determination that the workout audio playlist settingis enabled: stop playing the audio content on the device, and initiateplaying a workout audio playlist on the device; and in accordance with adetermination that the workout audio playlist setting is disabled,continue playing the audio content on the device.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; means for, while an audio application isplaying audio content, displaying a scrollable list of affordancesassociated with physical activities; means for, while the audioapplication is playing the audio content, receiving a user input at anaffordance of the scrollable list of affordances; and means for, inresponse to receiving the user input at the affordance: means forlaunching a physical activity tracking function associated with theselected affordance, and means for determining whether a workout audioplaylist setting is enabled; means for, in accordance with adetermination that the workout audio playlist setting is enabled: meansfor stop playing the audio content on the device, and means for initiateplaying a workout audio playlist on the device; and means for, inaccordance with a determination that the workout audio playlist settingis disabled, continue playing the audio content on the device.

In some embodiments, a method, comprising: at an electronic device witha display and a touch-sensitive surface: receiving, from an externaldevice, a message; and in accordance with a determination that themessage contains workout information: displaying one or more predefinedresponses to the received message; receiving user input corresponding toselecting a predefined response of the one or more predefined responses;and subsequent to receiving the user input, composing a reply message,wherein the reply message comprises: the selected predefined response;and the workout information.

In some embodiments, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display and a touch-sensitivesurface, the one or more programs including instructions for: receiving,from an external device, a message; and in accordance with adetermination that the message contains workout information: displayingone or more predefined responses to the received message; receiving userinput corresponding to selecting a predefined response of the one ormore predefined responses; and subsequent to receiving the user input,composing a reply message, wherein the reply message comprises: theselected predefined response; and the workout information.

In some embodiments, a transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display and a touch-sensitivesurface, the one or more programs including instructions for: receiving,from an external device, a message; and in accordance with adetermination that the message contains workout information: displayingone or more predefined responses to the received message; receiving userinput corresponding to selecting a predefined response of the one ormore predefined responses; and subsequent to receiving the user input,composing a reply message, wherein the reply message comprises: theselected predefined response; and the workout information.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; one or more processors; and memory storing oneor more programs configured to be executed by the one or moreprocessors, the one or more programs including instructions for:receiving, from an external device, a message; and in accordance with adetermination that the message contains workout information: displayingone or more predefined responses to the received message; receiving userinput corresponding to selecting a predefined response of the one ormore predefined responses; and subsequent to receiving the user input,composing a reply message, wherein the reply message comprises: theselected predefined response; and the workout information.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; means for receiving, from an external device, amessage; and means for, in accordance with a determination that themessage contains workout information: means for displaying one or morepredefined responses to the received message; means for receiving userinput corresponding to selecting a predefined response of the one ormore predefined responses; and means for, subsequent to receiving theuser input, composing a reply message, wherein the reply messagecomprises: the selected predefined response; and the workoutinformation.

In some embodiments, a method, comprising: at an electronic device witha display, a touch-sensitive surface, and a physical activity trackingsensor: displaying a scrollable list of affordances associated withheart rate information, the scrollable list of affordances comprising: afirst affordance identifying: a first physical activity, and first heartrate information associated with the first physical activity, whereinthe first heart rate information is measured by the physical activitytracking sensor; and a second affordance identifying: a second physicalactivity, and second heart rate information associated with the secondphysical activity, wherein the second heart rate information isdifferent than the first heart rate information, and wherein the secondheart rate information is measured by the physical activity trackingsensor; receiving user input; in accordance to a determination that theuser input corresponds to the first affordance, displaying additionalfirst heart rate information; and in accordance to a determination thatthe user input corresponds to the second affordance, displayingadditional second heart rate information, wherein the additional secondrate information is different than the additional first heart rateinformation.

In some embodiments, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, a touch-sensitivesurface, and a physical activity tracking sensor, the one or moreprograms including instructions for: displaying a scrollable list ofaffordances associated with heart rate information, the scrollable listof affordances comprising: a first affordance identifying: a firstphysical activity, and first heart rate information associated with thefirst physical activity, wherein the first heart rate information ismeasured by the physical activity tracking sensor; and a secondaffordance identifying: a second physical activity, and second heartrate information associated with the second physical activity, whereinthe second heart rate information is different than the first heart rateinformation, and wherein the second heart rate information is measuredby the physical activity tracking sensor; receiving user input; inaccordance to a determination that the user input corresponds to thefirst affordance, displaying additional first heart rate information;and in accordance to a determination that the user input corresponds tothe second affordance, displaying additional second heart rateinformation, wherein the additional second rate information is differentthan the additional first heart rate information.

In some embodiments, a transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, a touch-sensitivesurface, and a physical activity tracking sensor, the one or moreprograms including instructions for: displaying a scrollable list ofaffordances associated with heart rate information, the scrollable listof affordances comprising: a first affordance identifying: a firstphysical activity, and first heart rate information associated with thefirst physical activity, wherein the first heart rate information ismeasured by the physical activity tracking sensor; and a secondaffordance identifying: a second physical activity, and second heartrate information associated with the second physical activity, whereinthe second heart rate information is different than the first heart rateinformation, and wherein the second heart rate information is measuredby the physical activity tracking sensor; receiving user input; inaccordance to a determination that the user input corresponds to thefirst affordance, displaying additional first heart rate information;and in accordance to a determination that the user input corresponds tothe second affordance, displaying additional second heart rateinformation, wherein the additional second rate information is differentthan the additional first heart rate information.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; a physical activity tracking sensor; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: displaying a scrollable list of affordancesassociated with heart rate information, the scrollable list ofaffordances comprising: a first affordance identifying: a first physicalactivity, and first heart rate information associated with the firstphysical activity, wherein the first heart rate information is measuredby the physical activity tracking sensor; and a second affordanceidentifying: a second physical activity, and second heart rateinformation associated with the second physical activity, wherein thesecond heart rate information is different than the first heart rateinformation, and wherein the second heart rate information is measuredby the physical activity tracking sensor; receiving user input; inaccordance to a determination that the user input corresponds to thefirst affordance, displaying additional first heart rate information;and in accordance to a determination that the user input corresponds tothe second affordance, displaying additional second heart rateinformation, wherein the additional second rate information is differentthan the additional first heart rate information.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; a physical activity tracking sensor; means fordisplaying a scrollable list of affordances associated with heart rateinformation, the scrollable list of affordances comprising: a firstaffordance identifying: a first physical activity, and first heart rateinformation associated with the first physical activity, wherein thefirst heart rate information is measured by the physical activitytracking sensor; and a second affordance identifying: a second physicalactivity, and second heart rate information associated with the secondphysical activity, wherein the second heart rate information isdifferent than the first heart rate information, and wherein the secondheart rate information is measured by the physical activity trackingsensor; means for receiving user input; means for, in accordance to adetermination that the user input corresponds to the first affordance,displaying additional first heart rate information; and means for, inaccordance to a determination that the user input corresponds to thesecond affordance, displaying additional second heart rate information,wherein the additional second rate information is different than theadditional first heart rate information.

In some embodiments, a method, comprising: at an electronic device witha display, a touch-sensitive surface, and a physical activity trackingsensor: while tracking heart rate data corresponding to data receivedfrom the physical activity tracking sensor: determining whether theheart rate data satisfies a heart rate alert criteria; in accordance todetermining that the heart rate data satisfies the heart rate alertcriteria: displaying a heart rate alert affordance; receiving user inputcorresponding to the heart rate alert affordance; and subsequent toreceiving the user input corresponding to the heart rate alertaffordance, causing display of a graph comprising the heart rate datathat satisfies the heart rate alert criteria over a period of time; andin accordance to determining that the heart rate data does not satisfythe heart rate alert criteria, forgo causing display of the heart ratealert affordance.

In some embodiments, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, a touch-sensitivesurface, a physical activity tracking sensor, and the one or moreprograms including instructions for: while tracking heart rate datacorresponding to data received from the physical activity trackingsensor: determining whether the heart rate data satisfies a heart ratealert criteria; in accordance to determining that the heart rate datasatisfies the heart rate alert criteria: displaying a heart rate alertaffordance; receiving user input corresponding to the heart rate alertaffordance; and subsequent to receiving the user input corresponding tothe heart rate alert affordance, causing display of a graph comprisingthe heart rate data that satisfies the heart rate alert criteria over aperiod of time; and in accordance to determining that the heart ratedata does not satisfy the heart rate alert criteria, forgo causingdisplay of the heart rate alert affordance.

In some embodiments, a transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, a touch-sensitivesurface, a physical activity tracking sensor, and the one or moreprograms including instructions for: while tracking heart rate datacorresponding to data received from the physical activity trackingsensor: determining whether the heart rate data satisfies a heart ratealert criteria; in accordance to determining that the heart rate datasatisfies the heart rate alert criteria: displaying a heart rate alertaffordance; receiving user input corresponding to the heart rate alertaffordance; and subsequent to receiving the user input corresponding tothe heart rate alert affordance, causing display of a graph comprisingthe heart rate data that satisfies the heart rate alert criteria over aperiod of time; and in accordance to determining that the heart ratedata does not satisfy the heart rate alert criteria, forgo causingdisplay of the heart rate alert affordance.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; a physical activity tracking sensor; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: while tracking heart rate data correspondingto data received from the physical activity tracking sensor: determiningwhether the heart rate data satisfies a heart rate alert criteria; inaccordance to determining that the heart rate data satisfies the heartrate alert criteria: displaying a heart rate alert affordance; receivinguser input corresponding to the heart rate alert affordance; andsubsequent to receiving the user input corresponding to the heart ratealert affordance, causing display of a graph comprising the heart ratedata that satisfies the heart rate alert criteria over a period of time;and in accordance to determining that the heart rate data does notsatisfy the heart rate alert criteria, forgo causing display of theheart rate alert affordance.

In some embodiments, an electronic device, comprising: a display; atouch-sensitive surface; a physical activity tracking sensor; means for,while tracking heart rate data corresponding to data received from thephysical activity tracking sensor: means for determining whether theheart rate data satisfies a heart rate alert criteria; means for, inaccordance to determining that the heart rate data satisfies the heartrate alert criteria: means for displaying a heart rate alert affordance;means for receiving user input corresponding to the heart rate alertaffordance; and means for, subsequent to receiving the user inputcorresponding to the heart rate alert affordance, causing display of agraph comprising the heart rate data that satisfies the heart rate alertcriteria over a period of time; and means for, in accordance todetermining that the heart rate data does not satisfy the heart ratealert criteria, forgo causing display of the heart rate alertaffordance.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for displaying affordances associated with a physicalactivity, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace other methods for displaying affordancesassociated with a physical activity.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6BN illustrate exemplary user interfaces in accordance withsome embodiments.

FIG. 7 is a flow diagram illustrating a method for operating anelectronic device in accordance with some embodiments.

FIGS. 8A-8T illustrate exemplary user interfaces in accordance with someembodiments.

FIG. 9 is a flow diagram illustrating a method for operating anelectronic device in accordance with some embodiments.

FIGS. 10A-10N illustrate exemplary user interfaces in accordance withsome embodiments.

FIG. 11 is a flow diagram illustrating a method for operating anelectronic device in accordance with some embodiments.

FIGS. 12A-12M illustrate exemplary user interfaces in accordance withsome embodiments.

FIG. 13 is a flow diagram illustrating a method for operating anelectronic device in accordance with some embodiments.

FIGS. 14A-140 illustrate exemplary user interfaces in accordance withsome embodiments.

FIG. 15 is a flow diagram illustrating a method for operating anelectronic device in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for displaying affordances associated with a physicalactivity. Such techniques can reduce the cognitive burden on a user whoaccess the affordances associated with a physical activity, therebyenhancing productivity. Further, such techniques can reduce processorand battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-6BH illustrate exemplary user interfaces fordisplaying affordances associated with a physical activity. FIG. 7 is aflow diagram illustrating methods of displaying affordances associatedwith a physical activity in accordance with some embodiments. The userinterfaces in FIGS. 6A-6BH are used to illustrate the processesdescribed below, including the processes in FIG. 7.

FIGS. 8A-8T illustrate exemplary user interfaces for continuing or notcontinuing playing a currently playing song in response to selecting aworkout. FIG. 9 is a flow diagram illustrating methods of continuing ornot continuing playing a currently playing song in response to selectinga workout in accordance with some embodiments. The user interfaces inFIGS. 8A-8T are used to illustrate the processes described below,including the processes in FIG. 9.

FIGS. 10A-10N illustrate exemplary user interfaces for composing a replymessage that includes a predefined response and workout information.FIG. 11 is a flow diagram illustrating methods of composing a replymessage that includes a predefined response and workout information inaccordance with some embodiments. The user interfaces in FIGS. 10A-10Nare used to illustrate the processes described below, including theprocesses in FIG. 11.

FIGS. 12A-12M illustrate exemplary user interfaces for displayingaffordances associated with heart rate information. FIG. 13 is a flowdiagram illustrating methods of displaying affordances associated withheart rate information in accordance with some embodiments. The userinterfaces in FIGS. 12A-12M are used to illustrate the processesdescribed below, including the processes in FIG. 13.

FIGS. 14A-140 illustrate exemplary user interfaces for displaying aheart rate alert. FIG. 15 is a flow diagram illustrating methods ofdisplaying a heart rate alert in accordance with some embodiments. Theuser interfaces in FIGS. 14A-140 are used to illustrate the processesdescribed below, including the processes in FIG. 15.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700, 900,1100, 1300 and 1500 (FIGS. 7, 9, 11, 13, and 15). A computer-readablestorage medium can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. In some examples,the storage medium is a transitory computer-readable storage medium. Insome examples, the storage medium is a non-transitory computer-readablestorage medium. The non-transitory computer-readable storage medium caninclude, but is not limited to, magnetic, optical, and/or semiconductorstorages. Examples of such storage include magnetic disks, optical discsbased on CD, DVD, or Blu-ray technologies, as well as persistentsolid-state memory such as flash, solid-state drives, and the like.Personal electronic device 500 is not limited to the components andconfiguration of FIG. 5B, but can include other or additional componentsin multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “ITL”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT′D”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT′D”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “ITD”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “ITD”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6BN illustrate exemplary user interfaces associated with aphysical activity application, in accordance with some embodiments. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 7.

FIG. 6A illustrates device 600 with touch sensitive display 602. Userinterface 610A of a workout application is displayed on touch sensitivedisplay 602. Device 600 includes various input mechanisms that receiveuser input, such as rotatable input mechanism 603, which is able toreceive a rotatable input (and may also receive a push input), and inputmechanism 604, which is able to receive a push user input. In someembodiments, device 600 includes some or all of the features of device100, device 300, or device 500.

User interface 610A includes a scrollable list of affordances 620, whichare associated with respective physical activity tracking functions fora physical activity. For example, the scrollable list of affordancesincludes affordance 621, which corresponds to a physical activitytracking function for an outdoor run, and affordance 622, whichcorresponds to a physical activity tracking function for a pool swim. Itis noted that the scrollable list of affordances 620 includes additionalaffordances corresponding to other physical activity tracking functionsthat are not currently displayed but can be displayed in response to ascrolling input (e.g., rotation of rotational mechanism 603).

In some embodiments, one or more of the affordances in the scrollablelist of affordances 620 includes a respective change workout metricsaffordance, which will be described in further detail below (see atleast FIG. 6J). For example, affordance 621 includes change workoutmetrics affordance 631, and affordance 622 includes change workoutmetrics affordance 632.

In some embodiments, one or more affordances in the scrollable list ofaffordances 620 includes a physical activity icon corresponding to aphysical activity associated with the affordance. For example,affordance 621 includes physical activity icon 621-1 (e.g., icon of arunner). Similarly, affordance 622 includes physical activity icon 622-1(e.g., icon of a swimmer). In various embodiments, the physical activityicons (e.g., physical activity icon 621-1) are displayed in a firststate (e.g., static state).

In some embodiments, one or more affordances in the scrollable list ofaffordances includes a workout identifier. For example, affordance 621includes workout identifier 621-2 that indicates that affordance 621 isassociated with an outdoor run workout. Similarly, affordance 622includes workout identifier 622-2 that indicates that affordance 622 isassociated with a pool swim workout.

In some embodiments, one or more affordances in the scrollable list ofaffordances includes workout goal information. For example, affordance622 includes workout goal information 622-3 that indicates that the poolswim workout associated with affordance 622 has a predetermined goal ofthree miles. That is, when affordance 622 is selected, the associatedphysical activity tracking function will automatically track thedistance of the pool swim workout with a preset goal of three miles.Affordance 621 includes goal workout affordance 621-3 that indicatesthat the outdoor run associated with affordance 621 is an “open goal.”An open goal indication indicates to the user that the associatedworkout does not currently have any preset goals. Accordingly, whenaffordance 621 is selected, various metrics will be tracked by theassociated physical activity tracking function, wherein the metrics donot include any preset goal values.

Referring to FIG. 6B, touch input (e.g., tap input) 615A is received,wherein touch input 615A corresponds to selection of affordance 621. Inaccordance with a determination that user input 615A is detected atfirst affordance 621 in the scrollable list of affordances, a physicalactivity tracking function associated with affordance 621 is launched.That is, execution of the physical activity tracking function starts inaccordance to the selection of affordance 621. Moreover, in someembodiments, selection of another affordance (e.g., affordance 622) inthe scrollable list of affordances 620 will launch another associatedphysical activity tracking function, which will be described in furtherdetail below.

Referring to FIGS. 6C-6F, in response to selection of affordance 621,user interface 610B displays a countdown prior to tracking metrics bythe physical activity tracking function. For example, user interface610B displays “Ready” (FIG. 6C), then a numerical countdown bydisplaying “3” (FIG. 6D), then “2” (FIG. 6E), and then “1” (FIG. 6F).

In response to the completion of the countdown, user interface 610C isdisplayed (FIGS. 6G-6I). User interface 610 displays the tracked metrics630 (which are tracked by the physical activity tracking function)associated with the workout (e.g., outdoor run) corresponding to theselected affordance 621. For example, user interface 610C includes thetracking of various metrics (e.g., miles 630-1, active calories 630-2,average miles 630-3, and time 630-4). As shown in FIGS. 6G-6I, userinterface 610C displays tracked metrics 630 of the outdoor run workoutat time of 0.01 seconds into the outdoor run (FIG. 6G), at a time of0.59 seconds into the outdoor run (FIG. 6H), and a time of 1.23 secondsinto the outdoor run (FIG. 6H). In some embodiments, in response toselection of affordance 621, user interface 610C is displayed withoutdisplaying (or bypassing) user interface 610C.

Displaying a scrollable list of workout affordances and launching thephysical activity tracking function for tracking metrics associated witha selected workout affordance allows a user to quickly select a workoutand launch the tracking function to track the metrics associated withthe selected workout. Reducing the number of inputs needed to performtracking of workout metrics enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while the physical activity tracking functionassociated with the affordance is running, the physical activity icon isdisplayed in an animated state. For example, referring to FIGS. 6G-6I,while the physical activity tracking function is tracking metrics 630,physical activity icon 621-1 is animated (e.g., the runner in thephysical activity icon 621-1 moves in a running motion). It should beappreciated that physical activity icon 621-1 ceases to be animated whenthe physical activity tracking function associated with the affordancestops running (e.g., stops tracking metrics 630).

In some embodiments, the tracking of the metrics is performed by one ormore tracking sensors of the device. For example, device 600 tracks thephysical activity via tracking sensors (or workout sensors) thatcommunicate with workout support module 142 (as shown in FIG. 3).

Referring to FIG. 6J, user interface 610A displays scrollable list ofaffordances 620 (similar to FIG. 6A). User input 615B (e.g., tapgesture) is received at change workout metrics affordance 631.

Referring to FIG. 6K, in accordance to a determination that user input615B is detected at change workout metrics affordance 631, userinterface 610D is displayed, wherein user interface 610D is configuredto change workout metrics associated with a physical activity (e.g.,outdoor run) corresponding to affordance 621. In particular, userinterface 610D includes metric affordances 640 (e.g., open goalaffordance 640-1, distance affordance 640-2, calories affordance 640-3,and time affordance 640-4) that are associated with workout metricscorresponding with the outdoor run workout. User interface 610D alsoincludes affordance 641, which when selected, is configured to displayprevious UI 610A (FIG. 6J). In some embodiments, in accordance to adetermination that user input 615B is detected at change workout metricsaffordance 631, user interface 610D is displayed with launching thephysical activity tracking function associated with affordance 621.

Displaying a change workout metrics affordance with the scrollable listof workouts allows a user to quickly change goal values of a metric andlaunch the tracking function to track metrics associated with a workout.Reducing the number of inputs needed to change goal values and performtracking of workout metrics enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Referring to FIG. 6L, user input 615C (e.g., tap gesture) is received atdistance affordance 640-2.

Referring to FIGS. 6M-6R, in response to receiving user input 615C atdistance affordance 640-2, goal value user interface 610E is displayed.Goal value user interface 610E includes goal value 642 (e.g., 7.5 miles)corresponding to the selected distance affordance 640-2 of the outdoorrun workout. The initial goal value of 7.50 miles is the current valueassociated with the distance metric of the outdoor run. That is, if theoutdoor run workout was launched (with the distance goal value of 7.50miles) then the tracking of the distance metric would be set at 7.50miles.

In some embodiments, the goal value 642 (e.g., 7.50 miles) can beadjusted via goal change affordance 643 (e.g., “−” affordance) and/orgoal change affordance 644 (e.g., “+” affordance). For example, userinput 615D is received at goal change affordance 644 (FIG. 6N). Inresponse to receiving user input 615D at goal change affordance 644,goal value of 7.50 miles is changed to 7.60 miles (FIG. 6O). Similarly,user input 615E is received at goal change affordance 643 (FIG. 6P). Inresponse to receiving user input 615E at goal change affordance 643,goal value of 7.60 miles is changed to 7.50 miles (FIG. 6Q).

As shown in FIG. 6Q, goal value user interface 610E includes goalinformation 646. For example, goal information 646 is informationidentifying a previous longest distance (associated with the outdoor runworkout) that the physical activity tracking function has tracked.Accordingly, the user may adjust the goal value 642 (by increasing ordecreasing the goal value, as described above) based, at least in part,on goal information 646. Goal value user interface 610E also includesaffordance 645, which when selected, is configured to display previousUI 610D (FIG. 6L).

Referring to FIG. 6R, goal value user interface 610E includes startaffordance 647 configured to launch a physical activity trackingfunction associated with affordance 621. For example, user input 615H isreceived at start affordance 647. In response to user input 615Hselecting affordance 647, the physical activity tracking functionassociated with affordance 621 (e.g., outdoor run) is launched.Specifically, the physical activity tracking function tracks distancetraveled of the outdoor run based on the goal value of 7.50 miles. Insome embodiments, the launching of the physical activity trackingfunction associated with affordance 621, via start affordance 647, issimilar to the launching of the physical activity tracking function byuser input 615A at affordance 621 (e.g., FIGS. 6C-6I).

FIGS. 6S-6U depict various embodiments of goal value user interface610E. FIG. 6S depicts of user interface 610E displayed in response to auser input at open goal affordance 640-1 (FIG. 6K). The open goalfeature does not include any goal values associated with the physicalactivity (e.g., outdoor run). Accordingly, goal value user interface610E (when displayed in response to the selection of open goalaffordance 640-1) does not display any goal values. In response toreceiving user input 615I, at start affordance 647, the physicalactivity tracking function associated with affordance 621 (e.g., outdoorrun) is launched. The launched physical tracking function tracks variousmetrics (e.g., distance, calories, time) but does not track the metricswith respect to goal values. In some embodiments, the launching of thephysical activity tracking function associated with affordance 621, viastart affordance 647, is similar to the launching of the physicalactivity tracking function by user input 615A at affordance 621 (e.g.,FIGS. 6C-6I).

FIG. 6T depicts goal value user interface 610E displayed in response touser input at time goal affordance 640-4 (FIG. 6K). Goal user interface610E (when displayed in response to the selection of time goalaffordance 640-4) includes goal value 642 (e.g., elapsed time of onehour), goal change affordances 643 and 644, goal information 646 (e.g.,information identifying a previous longest time duration that thephysical activity tracking function has tracked for the outdoor run),and start affordance 647. Goal value 642 can be adjusted via selectionof goal change affordance 643 and/or goal change affordance 644 asdescribed above (FIGS. 6M-6Q). Additionally, in response to a user input(e.g., tap gesture) selecting affordance 647, the physical activitytracking function associated with affordance 621 (e.g., outdoor run) islaunched. Specifically, the physical activity tracking function trackstime duration of the outdoor run based on the goal value of one hour. Insome embodiments, the launching of the physical activity trackingfunction associated with affordance 621, via start affordance 647, issimilar to the launching of the physical activity tracking function byuser input 615A at affordance 621 (e.g., FIGS. 6C-6I).

FIG. 6U depicts user interface 610E displayed in response to a userinput at calories affordance 640-3 (FIG. 6K). Goal user interface 610E(when displayed in response to the selection of calories affordance640-3) includes goal value 642 (e.g., active calories burned), goalchange affordances 643 and 644, goal information 646 (e.g., informationidentifying the most calories burned that the physical activity trackingfunction has tracked from a previous outdoor run workout), and startaffordance 647. Goal value 642 can be adjusted via selection of goalchange affordance 643 and/or goal change affordance 644 as describedabove (FIGS. 6M-6Q). Additionally, in response to a user input (e.g.,tap gesture) selecting affordance 647, the physical activity trackingfunction associated with affordance 621 (e.g., outdoor run) is launched.Specifically, the physical activity tracking function tracks caloriesburned during the outdoor run based on the goal value of 700 calories.In some embodiments, the launching of the physical activity trackingfunction associated with affordance 621, via start affordance 647, issimilar to the launching of the physical activity tracking function byuser input 615A at affordance 621 (e.g., FIGS. 6C-6I).

FIGS. 6V-6AB depict an embodiment of user interface 610A displayingscrolling of the scrollable list of affordances 620 and selecting of anaffordance. For example, a rotational input 605 is received at rotatableinput mechanism 603 (FIGS. 6V-6W). In response to the rotational input605, the list of affordances 620 are scrolled in an upward directionsuch that affordance 622 is fully displayed, affordance 621 is partiallydisplayed, and affordance 623 (associated with a stair stepper workout)is partially displayed (FIG. 6X).

User input 615J is received at affordance 622 (FIG. 6Y). In response touser input 615J at affordance 622 (associated with a pool swim workout),user interface 610F is displayed (FIG. 6Z). User interface 610F includespool length value 648, value change affordance 643 and/or value changeaffordance 644. Pool length value 648 may be changed (e.g., from 50yards to 100 yards, from 50 yards to 25 yards, etc.) via the one or moreof the value change affordances. In particular, user interface 610F isconfigured to receive a pool length value (e.g., 50 yards) for the poolswim workout such that the physical activity tracking function can trackthe number of pool lengths that the user swims during the pool swimworkout.

User input 615K is received at start affordance 647 (FIG. 6AA). Inresponse to user input 615K, the physical activity tracking functionassociated with affordance 622 (e.g., pool swim) is launched. Forexample, in response to the selection of affordance 647, user interface610C is displayed (FIG. 6AB). User interface 610C includes tracking ofvarious metrics 633 (e.g., number of laps metric 633-1, active calories633-2, total calories 633-3, and time elapsed 633-4). It should beappreciated that a comparison between FIG. 6G (depicting tracked metrics630 associated with an outdoor run) and FIG. 6AB (depicting trackedmetrics 633 associated with a pool swim) shows that different physicalactivities can be tracked using different metrics. For example, for arunning activity it is often desirable to track the total length of therun (in miles), and for a pool swim it is often desirable to track thenumber laps completed.

FIGS. 6AC-6AD depict an embodiment of user interface 610A. Userinterface 610A displays affordances 624 and 625 in the scrollable listof affordances 620. In one embodiment, affordance 625 is not associatedwith a specific physical activity and is labeled “OTHER, Open Goal.”Additionally, in one embodiment, affordance 625 is the last (or bottom)affordance in the scrollable list of affordances 620. As will bedescribed in further detail below, affordance 625 facilitates inupdating the scrollable list of affordances 220 with an additionalspecific activity affordance, wherein the user is able to select thespecific physical activity (e.g., yoga) associated with the additionalspecific activity affordance.

User input 615L is received at affordance 625 (FIG. 6AD). In response touser input 615L, user interface 610G is displayed (FIG. 6AE). Userinterface 610G displays information 638 indicating that the user is ableto select a workout associated with the metrics that will be tracked bya physical activity tracking function. User interface 610G includesaffordance 647 configured to launch the physical activity trackingfunction.

User input 615M is received at affordance 647 (FIG. 6AF). In response touser input 615M, user interface 61B is displayed (FIG. 6AG). Userinterface 610B displays a countdown prior to tracking metrics by thephysical activity tracking function, as described above (e.g., FIGS.6C-6F).

Upon completion of the countdown, user interface 610C is displayed(FIGS. 6AH-6AI). User interface 610C is configured to display aplurality of metrics 634 (e.g., duration 634-1, active calories 634-2,total calories 634-3, and heart rate 634-4) tracked by the physicalactivity tracking function during the physical activity (e.g., yoga). Insome embodiments, user interface 610C is displayed in response to userinput 615M without display of intermediary user interface 610B. It isnoted that user interface 610C, as illustrated in FIGS. 6AH-6AI, doesnot include a physical activity icon (e.g., physical activity icon621-1) because affordance 625 is not associated with a physicalactivity.

User input 615N (e.g., a swipe gesture) is received on touch sensitivedisplay 602 (FIG. 6AI-6AK). In response to user input 615N, userinterface 610H is displayed (FIG. 6AL). User interface 610H includesaffordances to control various functionalities of the workoutapplication. For example, user interface 610H includes lock screenaffordance 650 (configured to lock the screen and not receive userinput), switch workout affordance 651 (described in further detailbelow), end workout affordance 652 (configured to end a currentlyrunning workout), and pause workout affordance 653 (configured to pausea currently running workout).

User interface 610C includes paging dots 639-1 and paging dot 639-2. Thepaging dots correspond to successive pages (or user interfaces) in theworkout application. For example, paging dot 639-1 corresponds to userinterface 610C, and paging dot 639-2 corresponds to user interface 610H.In response to user input, such as a swipe gesture (e.g., 610H), thecurrently displayed page (e.g., user interface 610C in FIG. 6AH) isreplaced with display of the corresponding successive page (e.g., userinterface 610H in FIG. 6AL). It is noted that, when user interface 610Cis displayed, paging dot 639-1 is highlighted (FIG. 6AH). Similarly,when user interface 610H is displayed, paging dot 639-2 is highlighted(FIG. 6AL).

User input 615O is received at end workout affordance 652 (FIG. 6AM).For example, upon completion of the user's yoga workout, the userselects end workout affordance 652 to stop tracking metrics 634. Inresponse to user input 615O at end workout affordance 652, userinterface 610I is displayed (FIG. 6AN).

User interface 610I includes a summary of the tracked metrics 634associated with affordance 625. For example, user interface 610Iincludes physical activity information 635 associated with metrics 634.Because tracked metrics 634 were tracked via selection of affordance 625(e.g., Other, Open Goal affordance), there is no physical activity(e.g., yoga) currently assigned or associated with tracked metrics 634of the completed workout. User interface 610I also includes duration634-1, active calories 634-2, total calories 634-3, average heart rate634-4, and range of heart rate 634-5. Additionally, user interface 610Iincludes add activity affordance 636 and done affordance 637. In someembodiments, user interface 610I includes the date and weatherinformation associated with the physical activity.

Note that the entirety of user interface 610I (including off-screenportions) is depicted in FIG. 6AN, for ease of discussion. However, itshould be appreciated the entirety of user interface 610I may not beable to displayed on the limited display size of touch sensitive display602. As a result, a user may scroll through the user interface via userinput (e.g., a rotatable input) received at rotatable input mechanism603.

User input 615P (e.g., tap gesture) is received at affordance 636 (FIG.6AO). Referring to FIG. 6AP, user interface 610I is displayed inresponse to user input 615P at affordance 636. User interface 610Idisplays a predefined list of selectable physical activities 660.Predefined list of selectable physical activities 660 is configured tobe selected and subsequently associated with the tracked metrics 634corresponding to affordance 625 (e.g., Other, Open Goal affordance).Predefined list of selectable physical activities 660 includes soccer660-1, yoga 660-2, strength 660-3, archery 660-4, basketball 660-5, andcurling 660-6. It is noted that the predefined list of selectablephysical activities 660 may include additional physical activities thatare not currently displayed but can be displayed in response to ascrolling input (e.g., rotation of rotational mechanism 603).

In some embodiments, the predefined list of selectable physicalactivities 660 includes a first set of physical activities (e.g., soccer660-1, yoga 660-2, and strength 660-3). The first set of physicalactivities, in some embodiments, is a predefined list of popularactivities and displayed at the top of the predefined list of selectablephysical activities 660. Additionally, the predefined list of selectablephysical activities 660 includes a second set of physical activities(e.g., archery 660-4, basketball 660-5, and curling 660-6) that islisted in alphabetical order.

Referring to FIGS. 6AQ and 6AR, user input 615Q is received at yogaactivity 660-2. In response to user input 615Q at yoga activity 660-2,metrics 634 of the completed workout are associated with a yoga workout.Accordingly, physical activity information 635 (in user interface 6601)indicates that metrics 634 are associated with a yoga workout viaselection of affordance 625. Additionally, in response to user input615Q at yoga activity 660-2, user interface 6601 includes icon 670 thatcorresponds to a yoga workout.

FIG. 6AT illustrates companion device 690 that is paired to device 600.In some embodiments, companion device 690 may be device 100, device 300,device 500, or a device that includes one or more features of thosedevices. Companion device 690 includes touch sensitive display 691. Userinterface 692 is displayed on touch sensitive display 691. Companiondevice 690, in some embodiments, when paired to device 600 is able todisplay the application views and perform at least some of the sameprocesses as device 600, as described, herein. In response to user input615R at affordance 637 (FIG. 6AS), summary information of the yogaworkout is displayed on user interface 692 of companion device 690. Forexample, user interface 692 includes icon 670 and metrics 634 associatedwith the completed yoga workout.

FIGS. 6AU-6AV illustrate an embodiment of user interface 610A. Inresponse to user input 615R at affordance 637 (FIG. 6AS), affordance 626is added to the scrollable list of affordances 620. For example,affordance 626 is a new affordance associated with a yoga workout.Affordance 626 is an open goal affordance associated with a yogaworkout. An open goal affordance is not associated with any predefinedgoal values. As such, in some embodiments, a physical activity trackingfunction tracks various metrics associated with the open goal affordanceand tracks the metrics without consideration of any predefined goalvalues. Affordance 626 is listed at the top or beginning of thescrollable list of affordances 620. In one embodiment, affordance 626 islisted at the bottom or end of the scrollable list of affordances 620.In various embodiments, affordance 625 remains listed in the scrollablelist of affordances upon adding a new affordance (e.g., affordance 626),wherein the new affordance is created, based, in part, on the selectionof affordance 625, as described herein.

User input 615S is received at affordance 626 (FIG. 6AV). In response touser input 615S, user interface 610B displays a countdown prior totracking metrics by the physical activity tracking function, asdescribed above (e.g., FIGS. 6C-6F). Upon completion of the countdowndisplayed in user interface 610B, a physical activity tracking functionis launched to track metrics 634 associated with a yoga workout (e.g.,duration 634-1, active calories 634-2, total calories 634-3, and heartrate 634-4) tracked by the physical activity tracking function duringthe physical activity (FIG. 6AX).

Referring to FIGS. 6AY-6BB, user input 61ST (e.g., swipe gesture) isreceived on touch sensitive display 602. In accordance to user input61ST, user interface 610H is displayed (FIG. 6BB). User interface 610Hincludes affordances to control various functionality of the workoutapplication. For example, user interface 610H includes lock screenaffordance 650, switch workout affordance 651, end workout affordance652, and pause workout affordance 653.

User input 615U is received at switch workout affordance 651 (FIG. 6BC).For example, while the physical activity tracking function is trackingmetrics 634 during the user's yoga workout, the user selects switchworkout affordance 651 to switch to a different workout. In response touser input 615U at switch workout affordance 651, user interface 610A isdisplayed (FIG. 6BD) displaying the scrollable list of affordances 620(e.g., affordance 621 and affordance 622). Additionally, in response touser input 615U at switch workout affordance 651, the physical activitytracking function tracking metrics 634 is paused.

FIG. 6BD illustrates user interface 610A that includes paused physicalactivity affordance 655. In one embodiment, user input at affordance 655is configured to continue the paused workout (e.g., paused yogaworkout). For example, in response to user input at affordance 655, thepaused physical activity tracking function associated with the yogaworkout resumes tracking metrics 634 (e.g., FIG. 6AY).

Referring to FIGS. 6BE-6BG, user input 615V is received at affordance621 (FIG. 6BE). In response to user input 615V at affordance 621, aphysical activity tracking function is launched to track metrics 630(e.g., miles 630-1, active calories 630-2, average miles 630-3, and time630-4) of the corresponding physical activity (e.g., outdoor run).Additionally, in response to user input 615V at affordance 621 (FIG.6BE), the paused workout (e.g., paused yoga workout) is cancelled.Specifically, the physical activity tracking function associated withtracking metrics 634 is cancelled.

Referring to FIG. 6BH, user interface 610H is displayed. For example,user interface 610H is displayed in response a swipe gesture on touchsensitive display 602 in FIG. 6BG.

User input 615W is received at end workout affordance 652 (FIG. 6BH). Inresponse to user input 615W at end workout affordance 652, tracking ofmetrics 630 is ended, and user interface 610J is displayed (FIG. 6BI).User interface 610J is configured to display a summary of aggregatedmetrics of at least two previously completed workouts. For example, userinterface 610J includes aggregated metrics 680 (e.g., total time 680-1,active calories 680-2, total calories 680-3, average heart rate 680-4,and heart rate range 680-5) that include an aggregation of the metrics630 associated with the outdoor run workout and metrics 634 associatedwith the yoga workout. In one embodiment, a user switched from the yogaworkout to the outdoor run workout via selection of switch affordance651 (FIG. 6BC).

User interface 610J includes workout affordance 681 associated with theyoga workout and affordance 682 associated with the outdoor run workout.User input 615W is received at affordance 682 corresponding to theoutdoor run workout. In response to user input 615W at affordance 682,user interface 610K is displayed (FIG. 6BK). User interface 610Kincludes metrics 630 (e.g., total time, average pace, active calories,total calories, average heart rate, and heart rate range) associatedwith the outdoor run. Similarly, in some embodiments, in response touser input at affordance 681, metrics 634 associated with the yogaworkout would be displayed (e.g., similar to displayed metrics 634 inFIG. 6AS).

Referring to FIGS. 6BL-6BM, device 600 is in proximity to pairableworkout device 695 (e.g., external heart rate monitor, treadmill, stairstepper). Device 600 and device 695 are communicatively pairable. Forexample, device 600 and device 695 are pairable via a wirelesscommunication (e.g., near-field communication (NFC), Bluetooth). Itshould be appreciated that device 690 may also be pairable to workoutdevice 695.

Device 600 detects pairable workout device 695 when device 600 is inclose proximity to device 695. In response to detecting pairable workoutdevice 695 and in accordance with a determination that an automaticworkout device pairing criteria is satisfied, device 600 isautomatically paired (e.g., without additional user input) with pairableworkout device 695 (FIG. 6BM). For example, device 695 is automaticallypaired with device 695 (e.g., external heart rate monitor). Accordingly,device 600 displays information 696 indicating that device 600 anddevice 695 have been automatically paired with one another.

In one embodiment, the automatic workout device pairing criteria issatisfied when a workout (e.g., outdoor run workout) has been completedon device 600. In another embodiment, the automatic workout devicepairing criteria is satisfied when device 600 has been paired withpairable workout device 695 within a predetermined time (e.g., withinthe past 90 days). In a further embodiment, the automatic workout devicepairing criteria is satisfied when a user affirmatively enables asetting for automatic pairing with pairable workout devices.

In some embodiments, in response to detecting pairable workout device695 and in accordance with a determination that an automatic workoutdevice pairing criteria is not satisfied, device 600 is notautomatically paired with pairable workout device. In one embodiment,the automatic workout device pairing criteria is not satisfied when aworkout (e.g., outdoor run workout) has not been previously completed ondevice 600. In another embodiment, the automatic workout device pairingcriteria is not satisfied when device 600 has not been paired withpairable workout device 695 within a predetermined time (e.g., withinthe past 90 days). In a further embodiment, the automatic workout devicepairing criteria is not satisfied when a user does not affirmativelyenable a setting for automatic pairing with pairable workout devices. Inanother embodiment, the automatic workout device pairing criteria is notsatisfied when a user selects a workout affordance (e.g., affordance621) and the user is prompted to provide user input to connect with thepairable workout device 695 (e.g., heart monitor). For example,referring to FIG. 6BN, accept pairing affordance 696-1 (e.g., Yes), anddecline pairing affordance 696-2 (e.g., not now) are displayed. Devices600 and 695 will be paired in accordance to user selection of acceptpairing affordance 696-1. Alternatively, devices 600 and 695 will not bepaired in accordance to user selection of decline pairing affordance696-2.

FIG. 7 is a flow diagram illustrating a method for displaying ascrollable list of affordances associated with physical activities usingan electronic device in accordance with some embodiments. Method 700 isperformed at a device (e.g., 100, 300, 500, 600) with one or moreprocessors, memory and a physical activity tracking sensor. Someoperations in method 700 are, optionally, combined, the order of someoperations are, optionally, changed, and some operations are,optionally, omitted.

As described below, method 700 provides, among other things, anintuitive way for launching a physical activity tracking function inaccordance with a determination that the user input is detected at afirst affordance in the scrollable list of affordances. The methodreduces the cognitive burden on a user by selecting a workout from alist of workouts and launching a physical activity tracking function,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to select a workoutfrom a list of workouts and launch a physical activity tracking functionfaster and more efficiently conserves power and increases the timebetween battery charges.

At block 710, the device (e.g., 600) displays a scrollable list ofaffordances (e.g., 620) associated with physical activities.

At block 720, the device displays a first change workout metricsaffordance (e.g., 631) corresponding to a first affordance (e.g., 621)of the scrollable list of affordances (e.g., 620).

At block 730, the device (e.g., 600) receives a user input (e.g., 615A).

At block 740, in accordance with a determination that the user input(e.g., 615A) is detected at the first affordance (e.g., 221) in thescrollable list of affordances (e.g., 220), a physical activity trackingfunction associated with the selected first affordance is launched(e.g., the physical activity tracking function tracks metrics 630).

At block 750, in accordance with a determination that the user input(e.g., 615B) is detected at the first change workout metrics affordance(e.g., 631), a user interface (e.g., 610D) configured to change aworkout metric is displayed.

In some embodiments, user input (e.g., 615L) is received at a secondaffordance (e.g., 625) in the scrollable list of affordances. Inresponse to the user input at the second affordance, the device (e.g.,600) launches a physical activity tracking function associated with theselected second affordance. Subsequent to completion of the trackingfunction, the device displays a predefined list of selectable physicalactivities (e.g., 660). User input (e.g., 615Q) is received at aselectable physical activity (e.g., 660-2) of the predefined list ofselectable physical activities. Subsequent the selection of the physicalactivity in the predefined list of selectable physical activities, thedevice updates the scrollable list of affordances (e.g., 220) with anadditional affordance (e.g., 626) associated with the selected physicalactivity.

In accordance with some embodiments, in accordance with a determinationthat the user input (e.g., 615B) is detected at the first change workoutmetrics affordance (e.g., 631), the device forgoes launching of thephysical activity tracking function associated with the first affordance(e.g., 621).

In some embodiments, user input (e.g., 615C) corresponding withselecting a metric affordance (e.g., 640-2) of the plurality of metricaffordances (e.g., 640) is received. In response to receiving the userinput corresponding with selecting the metric affordance, the device(e.g., 600) displays a first goal value (e.g., 642) corresponding to theselected metric affordance.

In some embodiments, in response to receiving the user inputcorresponding with selecting the metric affordance (e.g., 615C), thedevice (e.g., 600) displays at least one goal change affordance (e.g.,643 or 644). User input (e.g., 615D) corresponding with selecting the atleast one goal change affordance in received. In response to receivingthe user input corresponding with the at least one goal changeaffordance, the first goal value (e.g., goal value of 7.50 miles) isreplaced with a second goal value (e.g., goal value of 7.60 miles).

In some embodiments, further in response to receiving the user input(e.g., 615C) corresponding with selecting the metric affordance (e.g.,640-2), the device (e.g., 600) displays a start physical activitytracking affordance (e.g., 647) corresponding with launching a physicalactivity tracking function associated with the selected firstaffordance. User input (e.g., 615H) is received corresponding withselecting the start physical activity tracking function affordance. Inresponse to receiving the user input corresponding with selecting thestart physical activity tracking function affordance, a physicalactivity tracking function associated with the selected first affordanceis launched (e.g., device 600 tracks metrics 630 associated with anoutdoor run workout).

In some embodiments, launching the physical activity tracking functionassociated with the selected first affordance (e.g., 621) includestracking a first set of metrics (e.g., 630) associated with a first typeof physical activity (e.g., outdoor run). In accordance with adetermination that the user input is detected at a second affordance(e.g., 622) in the scrollable list of affordances (e.g., 620), aphysical activity tracking function associated with the selected secondaffordance is launched, including tracking a second set of metrics(e.g., 633) associated with a second type of physical activity (e.g.,pool swim). The second set of metrics (e.g., 633) is different than thefirst set of metrics (e.g., 630).

In some embodiments, an affordance (e.g., 621) in the scrollable list ofaffordances includes a physical activity icon (e.g., 621-1)corresponding to a physical activity (e.g., outdoor run) associated withthe affordance. In some embodiments, while a physical activity trackingfunction associated with the affordance is running, the physicalactivity icon (e.g., 621-1) is displayed in an animated state.

In some embodiments, while a physical activity tracking functionassociated with an affordance (e.g., 626) is running, user input (e.g.,615T) is received corresponding to a request to display a user interface(e.g., 610H) configured to switch workouts. In response to receiving theuser input corresponding to a request to display a user interfaceconfigured to switch workouts, the physical activity tracking functionis paused, and a switch workout affordance (e.g., 651) is displayed.User input (e.g., 615U) corresponding to selecting the switch workoutaffordance is received. In response to receiving the user inputcorresponding to selecting the switch workout affordance, the scrollablelist of affordances (e.g., 620) is displayed, and a paused physicalactivity affordance (e.g., 655) associated with the paused physicaltracking function is displayed.

In some embodiments, subsequent to pausing the physical activitytracking function, user input (e.g., 615V) corresponding to selection ofan affordance (e.g., 621) in the scrollable list of affordances (e.g.,620) is received. In response to receiving the user input correspondingto the selection of the affordance in the scrollable list ofaffordances, the paused physical activity tracking function is cancelled(e.g., stop tracking metrics 634 for a yoga workout), and a differentphysical activity tracking function associated with the selectedaffordance is launched (e.g., start tracking metrics 630 for an outdoorrun).

In some embodiments, user input corresponding to selection of the pausedphysical activity affordance (e.g., 655) is received. In response toreceiving the user input corresponding to selection of the pausedphysical activity affordance, the paused physical activity trackingfunction is resumed (e.g., tracking of metrics 634 resumes).

In some embodiments, subsequent completion of a first workout trackingfunction and a second workout tracking function, a scrollable workoutsummary (e.g., summary of aggregated metrics 680) of a first physicalactivity associated with the first workout tracking function and asecond physical activity associated with the second workout trackingfunction is displayed. The scrollable workout summary includes a set ofaggregated metrics (e.g., 680) of the first workout tracking functionand the second workout tracking function, a first affordance associatedwith the first physical activity (e.g., 681), and a second affordanceassociated with the second physical activity (e.g., 682). User input isreceived (e.g., 615W). In accordance to determination that the userinput (e.g., 615W) corresponds to selection of the first affordanceassociated with the first physical activity (e.g., 681), a set ofmetrics associated with the first physical activity is displayed (e.g.,630 in FIG. 6BK). In accordance to determination that the user input(e.g., 615W) corresponds to selection of the second affordanceassociated with the second physical activity (e.g., 682), a set ofmetrics associated with the second physical activity is displayed (e.g.,634).

In some embodiments, a pairable workout device (e.g., 695) is detected.In response to detecting the pairable workout device and in accordancewith a determination that an automatic workout device pairing criteriais satisfied (e.g., a workout has been completed on device 600, device600 has been paired with pairable workout device 695 within apredetermined time, or the user affirmatively enables a setting forautomatic pairing with pairable workout devices), the device (e.g., 600)is automatically paired with the pairable workout device. In response todetecting the pairable workout device (e.g., 695) and in accordance witha determination that an automatic workout device pairing criteria is notsatisfied (e.g., a workout has not been previously completed on device600, device 600 has not been paired with pairable workout device 695within a predetermined time, a user does not affirmatively enable asetting for automatic pairing, or the user is prompted to provide userinput to connect with the pairable workout device), forgo automaticpairing the device with the pairable workout device (FIG. 6BN).

In some embodiments, the user interface configured to change a workoutmetric (e.g., 610D) includes a plurality of metric affordances (e.g.,640-1, 640-2, 640-3, and 64-4) corresponding to the physical activityassociated with the first affordance (e.g., 621). In some embodiments,the physical activity tracking function tracks metrics (e.g., 630)corresponding to data received from the physical activity trackingsensor (e.g., sensors of workout support module 142). In someembodiments, the first affordance (e.g., 621) in the scrollable list ofaffordances (e.g., 620) is the most recently selected affordance.

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7) are also applicable in an analogous manner tothe methods described below. For example, method 900 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 700. For example, method 900, in someembodiments, may include launching a physical activity tracking functionor displaying a user interface configured to change a workout metric.For brevity, these details are not repeated below.

FIGS. 8A-8T illustrates exemplary user interfaces associated with aphysical activity application and an audio application, in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIG. 9.

FIG. 8A illustrates device 800 with touch sensitive display 802. Device800 includes various input mechanisms that receive user input, such asrotatable input mechanism 803, that is able to receive a rotatable input(and may also receive a push input), and input mechanism 804 that isable to receive a push user input. In some embodiments, device 800includes some or all of the features of device 100, device 300, device500, or device 600.

Referring to FIG. 8A, user interface 810A, displayed on touch sensitivedisplay 802, is an audio application control user interface configuredto control audio content playing on the audio application. Userinterface 810A includes audio content information 811 and audio contentcontrols 812. For example, audio content information 811 includes, butis not limited to, the title of the currently playing audio content(e.g., “Across the Land”) and the name of the group (e.g., “AweSingers”) performing the song. Audio content controls 812 includes butare not limited to, jump forward to next song, pause/play, jump backwardto previous song, and volume control.

User input 815A (e.g., push input via finger 816) is received atrotatable input mechanism 803 (FIG. 8B). In response to user input 815Aand while audio content is playing on the audio application, userinterface 810B is displayed (FIG. 8C). User interface 810B includes aplurality of application affordances 805 associated with applications.For example, affordance 805-1 is associated with a workout application,and affordance 805-2 is associated with the audio application currentlyplaying the audio content.

User input 815B (e.g., tap gesture) is received at affordance 805-1(FIG. 8D). In response to user input 815B at affordance 805-1 and whilethe audio content is playing on the audio application, user interface810C is displayed (FIG. 8E). User interface 810C includes a scrollablelist of affordances 820 that are associated with respective physicalactivity tracking functions for a physical activity. For example, thescrollable list of affordances includes affordance 821, whichcorresponds to a physical activity tracking function for an outdoor run,and affordance 822, which corresponds to a physical activity trackingfunction for a pool swim. It is noted that the list of affordances 820includes additional affordances corresponding to other physical activitytracking functions that are not currently displayed but can be displayedin response to a scrolling input (e.g., rotation of rotational mechanism803).

In some embodiments, one or more of the affordances in the scrollablelist of affordances 820 includes a respective change workout metricsaffordance. For example, affordance 821 includes change workout metricsaffordance 831, and affordance 822 includes change workout metricsaffordance 832. In one embodiment, user interface 810C is the same asuser interface 610A (FIG. 6A). Accordingly, user interface 810C includesthe same features and functionality as user interface 610A, as describedabove.

In some embodiments, while the audio content is currently playing ondevice 800, device 800 receives an enabled setting of the workout audioplaylist setting from an external device (e.g., companion device 890),which will be described in further detail below (FIGS. 8N-8T). When theworkout audio playlist setting is enabled, a workout playlist willautomatically play in response to selection of a workout affordance. Inone embodiment, a workout audio playlist is a list of audio content(e.g., a list of songs) selected by the user to be played during aworkout.

User input 815C is received at affordance 821 (FIG. 8F). In response touser input 815C, user interface 810D is displayed (FIG. 8G). Userinterface 810D (similar to user interface 610B) displays a countdownprior to tracking metrics by the physical activity tracking functionassociated with affordance 821. In one embodiment, user interface 810Dis the same as user interface 610B (FIGS. 6C-6F). Accordingly, userinterface 810D includes the same features and functionality as userinterface 610B, as described above.

In response to completion of the countdown, user interface 810E isdisplayed (FIG. 8H). User interface 810E is configured to display aplurality of metrics 830 (e.g., miles 830-1, active calories 830-2,average miles 830-3, and time 830-4) tracked by the physical activitytracking function during the physical activity (e.g., outdoor run). Inone embodiment, user interface 810E is the same as user interface 610C(FIGS. 6G-6I). Accordingly, user interface 810E includes the samefeatures and functionality as user interface 610C, as described above.In one embodiment, user interface 810E is displayed in response to userinput 815C without display of intermediary user interface 610D.

Additionally, in response to user input 815C (FIG. 8F), the audioapplication stops playing the currently playing song (e.g., “Across theLand”) and initiates playing the workout audio playlist. For example,the currently playing song (e.g., “Across the Land”) is not a songlisted in the workout playlist. Accordingly, the currently playing songis canceled and replaced with playing of a song in the workout playlist.

Referring to FIGS. 8I-8L, user input 815D (e.g., swipe gesture) isreceived on touch sensitive display 802 while the physical activitytracking function is running (e.g., tracking metrics associated with theoutdoor run workout) and the audio application is playing audio content.In response to user input 815D, user interface 810A is displayed. Userinterface 810A displays audio content from the workout audio playlistbecause playing of the workout audio playlist was initiated in responseto user input 815C (as described above). In particular, user interface810A includes audio content information 811 corresponding to the song“Feel the Burn” performed by “Drill Sergeant” from the workout audioplaylist. It is noted that user interface 810A includes volume control813 configured to control the volume of the currently playing song.

In some embodiments, when the setting is not enabled, the currentlyplaying song continues to play, as seen in FIG. 8M.

Referring to FIGS. 8I-8K, user interface 810E includes paging dots839-1, 839-2, and 839-3. The paging dots correspond to successive pages(or user interfaces). For example, paging dot 839-1 corresponds to aworkout control user interface (e.g., similar to user interface 610H),paging dot 839-2 corresponds to user interface 810E, and paging dot839-3 corresponds to user interface 810A. In response to user input,such as swipe gesture 815D, the currently displayed user interface 610E(FIG. 8I) is replaced with a display of the corresponding successiveuser interface 810A (FIG. 8K). It is noted, that when user interface810E is displayed, paging dot 839-2 is highlighted (FIG. 8I). Similarly,when user interface 810A is displayed, paging dot 839-3 is highlighted(FIG. 8L).

FIGS. 8N-8T illustrate embodiments of companion device 890 that ispaired to device 800. In some embodiments, companion device 890 may bedevice 100, device 300, device 500, or a device that includes one ormore features of those devices. Companion device 890 includes touchsensitive display 891. User interface 892A is displayed on touchsensitive display 891. Companion device 890, in some embodiments, whenpaired to device 800, is able to display the application views andperform at least some of the same processes as device 800, as describedherein. In some embodiments, a setting (e.g., enabled or disabled) ofthe workout audio playlist setting is received from companion device 890(as described above).

Referring to FIG. 8N, user interface 892A includes a plurality ofaffordances 893 associated with respective applications (e.g., watchapplication, camera application, weather application, clock application,phone application, message application, mail application, and browserapplication). In one embodiment, affordance 893-1 is associated with awatch application (e.g., watch application for controlling variousfeatures and functionality of device 800).

User input 815F is received at affordance 893-1 (FIG. 8O). In responseto user input 815F at affordance 893-1, user interface 892B is displayed(FIG. 8P). User interface 892B includes device information 860 (e.g.,information related to device 800 that is paired with device 892), watchfaces 861 (e.g., various watch faces that are enabled to be displayed ondevice 800), and a list of application affordances 862 that correspondto applications installed on device 800. The list of applicationaffordances 862, in some embodiments, corresponds, at least in part, tothe plurality of application affordances 805 displayed on user interface810B on device 800 (FIG. 8C). List of application affordances 862includes affordance 862-1 that corresponds to a workout applicationinstalled on device 800.

User input 815G (e.g., tap gesture) is received at affordance 862-1(FIG. 8Q). In response to user input 815G at affordance 862-1, userinterface 892C is displayed (FIG. 8R). User interface 892C includesvarious workout application settings associated with the workoutapplication installed on device 800. In one embodiment, user interface892C includes workout audio playlist setting 870 (e.g., “WorkoutPlaylist Auto Play”). As illustrated in FIG. 8R, the setting of workoutaudio playlist setting 870 is enabled. Accordingly, when workout audioplaylist setting 870 is enabled (at device 890) the workout audioplaylist is automatically played by the audio application (at device800) in response to selection of an affordance (e.g., affordance 821) inthe scrollable list of affordances 820, as described above. In oneembodiment, the setting of workout audio playlist setting 870 (e.g.,enabled setting) corresponds to a default setting at device 890. Inanother embodiment, the setting of workout audio playlist setting 870(e.g., enabled setting) corresponds to user-selected settings at device890.

User interface 892C includes running auto pause setting 871. Forexample, when it is determined that running auto pause setting 871 isenabled, tracking of metrics associated with a running workout isautomatically paused when it is determined that the user has stoppedrunning for a predetermined amount of time (e.g., three seconds).Alternatively, when it is determined that running auto pause setting 871is disabled, tracking of metrics associated with a running workoutcontinues (not automatically paused) when it is determined that the userhas stopped running for a predetermined amount of time (e.g., threeseconds).

Automatically stopping a song playing on a device and initiating playingof a workout audio playlist on the device in response to selection of aworkout when workout playlist setting is enabled provides the user withmore control of the device by simultaneously allowing the user to stop acurrently playing song and automatically initiate playing the workoutplaylist. Automatically stopping a song playing on a device andinitiating playing of a workout audio playlist on the device in responseto selection of a workout when workout playlist setting is enabledwithout requiring further user input enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device), which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

Referring to FIG. 8S, user input 815H is received at workout audioplaylist setting 870. User input 815H is to switch the workout audioplaylist setting from enabled to disabled (or from disabled to enabled).Referring to FIG. 8T, in response to user input 815H, workout audioplaylist setting 870 is set to disabled. Accordingly, when workout audioplaylist setting 870 is disabled (at device 890), the workout audioplaylist is not automatically played by the audio application (at device800) in response to selection of an affordance (e.g., affordance 821) inthe scrollable list of affordances 820, as described above. For example,when workout audio playlist setting 870 is disabled (at device 890), asong (e.g., “Across the Land”) currently playing by the audioapplication (at device 800) remains playing without interruption inresponse to selection of an affordance (e.g., affordance 821) in thescrollable list of affordances 820, as described above. In oneembodiment, the setting of workout audio playlist setting 870 (e.g.,disabled setting) corresponds to a default setting at device 890.

FIG. 9 is a flow diagram illustrating a method for, in response toselecting a workout affordance, automatically playing a workout playlistbased on a workout playlist setting. Method 900 is performed at a device(e.g., 100, 300, 500, 600, and 800) with one or more processors andmemory. Some operations in method 900 are, optionally, combined, theorder of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 900 provides, among other things, anintuitive way for, in response to selecting a workout affordance,automatically playing a workout playlist based on a workout playlistsetting. The method reduces the cognitive burden on a user byautomatically playing a workout playlist based on a workout playlistsetting, thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to select a workoutfrom a list of workouts and launch a physical activity tracking functionfaster and more efficiently conserves power and increases the timebetween battery charges.

At block 910, while an audio application is playing audio content (e.g.,“Across the Land”), the device 800 displays a scrollable list ofaffordances (e.g., 820) associated with physical activities.

At block 920, while the audio application is playing the audio content,a user input (e.g., 815C) is received at an affordance (e.g., 821) ofthe scrollable list of affordances.

At block 930, in response to receiving the user input at the affordance,a physical activity tracking function associated with the selectedaffordance is launched, and it is determined whether a workout audioplaylist setting is enabled (e.g., enabled setting is received fromdevice 890).

At block 940, in accordance with a determination that the workout audioplaylist setting is enabled, the audio content currently playing on thedevice (e.g., “Across the Land”) is stopped, and playing a workout audioplaylist is initiated (e.g., playing of “Feel the Burn”) on the device(e.g., device 800). At block 950, in accordance with a determinationthat the workout audio playlist setting is disabled (e.g., disabledsetting is received from device 890), the audio content currentlyplaying on the device is continued (e.g., “Across the Land”).

In some embodiments, while the physical activity tracking function isrunning (e.g., tracking metrics 830) and the audio application isplaying audio content (e.g., “Across the Land” is playing), user input(e.g., 815D) is received corresponding to a request to display an audioapplication control user interface (e.g., 810A), and, in response to theuser input (e.g., 815D), the audio application control user interface(e.g., 810A) of the audio application playing the audio content isdisplayed.

In some embodiments, prior to receiving user input (e.g., 815C) at anaffordance (e.g., 821), a setting of the workout audio playlist setting(e.g., enabled or disabled) is received from an external device (e.g.,890).

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9) are also applicable in an analogous manner tothe methods described below. For example, method 900 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 1300. For example, the tracking ofmetrics by a physical activity tracking function in method 900 may alsotrack heart rate information, as described in method 1300. For brevity,these details are not repeated below.

FIGS. 10A-10N illustrate exemplary user interfaces associated with amessaging application, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 11.

FIG. 10A illustrates device 1000 with touch sensitive display 1002.Device 1000 includes various input mechanisms that receive user input,such as rotatable input mechanism 1003, that is able to receive arotatable input (and may also receive a push input), and input mechanism1004 that is able to receive a push user input. In some embodiments,device 1000 includes some or all of the features of device 100, device300, device 500, device 600, or device 800.

FIG. 10A includes user interface 1010A. User interface 1010A includes amessage 1020 (e.g., text message or email) received from an externaldevice. Message 1020 includes workout information. For example, workoutinformation includes information identifying a person 1020-1 (e.g.,“John completed a workout!”), type of workout 1020-2 (e.g., “OutdoorRun”), and workout metrics 1020-3 (e.g., 3.00 miles, 326 activecalories, and 351 total calories).

In some embodiments, the external device (that sent message 1020)includes some or all of the features of device 1000 (or device 100,device 300, or device 500). In one embodiment, the external device is adevice that is a companion device to another external device (e.g.,companion device 690 described above). In one embodiment, message 1020is composed by a workout application (or workout tracking application)on the external device, wherein the workout application generates theworkout information contained in message 1020. Further, in oneembodiment, the workout application on the external device includes someor all of the features as a workout application described herein (e.g.,workout application as shown in at least FIG. 6A).

User interface 1010A also includes reply affordance 1022-1 (e.g.,configured to enable a user to generate a reply message), muteaffordance 1022-1 (e.g., configured to mute subsequent messages from theexternal device), and dismiss affordance 1022-3 (e.g., configured todismiss message 1020 without sending a reply message).

User input 1015A is received at reply affordance 1022-1 (FIG. 10B).Referring to FIGS. 10C-10D, in response to user input 1015A at replyaffordance 1022-1 and in accordance with a determination that message1020 contains workout information, user interface 1010B is displayed.User interface 1010B is configured to enable a user to compose a replymessage to message 1020. User interface 1010B includes a list ofpredefined responses 1030 corresponding to message 1020 that includesworkout information. Predefined responses 1030, in some embodiments,includes predefined response 1030-1 (e.g., “how′d you get so good”),predefined response 1030-2 (e.g., “#goals”), predefined response 1030-3(e.g., “Hands down, you're the best”), predefined response 1030-4 (e.g.,“what's your secret?”), predefined response 1030-5 (e.g., “Hello!”),predefined response 1030-6 (e.g., “what's up?”), predefined response1030-7 (e.g., “on my way”), and predefined response 1030-8 (e.g., “ok”).

Additionally, user interface 1010B includes affordance 1031 configuredto enable a user to record an audio reply to message 1020, affordance1032 configured to enable a user to select emojis for a reply message tomessage 1020, affordance 1033 configured to enable a user to send ahandwritten reply message (or sticker) to message 1020, and affordance1034 configured to enable a user to send a reply message (that includestext generated from handwriting input) to message 1020.

In one embodiment, in accordance to a determination that message 1020does not contain workout information (e.g., a text that includes “HiJane”), the message is displayed at device 1000. However, predefinedresponses 1030 are not displayed at device 1000.

As shown in FIG. 10D, user input 1015B is received at predefinedresponse 1030-2. In response to user input 1015B at predefined response1030-2, a reply message to message 1020 is composed (e.g., reply message1050 in FIG. 10E). In one embodiment, subsequent to receiving user input1015B at predefined response 1030-2, an intermediary user interface isdisplayed that prompts the user to compose the reply message. Inresponse to user input to compose the reply message, the reply messageis composed.

FIGS. 10E-10F depict user interface 1010C (e.g., text message userinterface) displayed at companion device 1065 (e.g., companion device todevice 1000) and external device 1090. Referring to FIG. 10E, replymessage 1050 is displayed at companion device 1065. In one embodiment,reply message 1050 is displayed at device 1000. Reply message 1050includes selected predefined message 1030-2 (e.g., “#goals” selected atdevice 1000, FIG. 10C) and workout information, such as informationidentifying a person 1020-1 (e.g., “John”), type of workout 1020-2(e.g., “Outdoor Run”), and workout metrics 1020-3 (e.g., 3.00 miles). Atcompanion device 1065, reply message 1050 is displayed in-line withother messages (from external device 1090). Referring to FIG. 10F, replymessage 1050 is received at external device 1090 and displayed atexternal device 1090. At external device 1090, reply message 1050 isdisplayed in-line with other messages (from companion device 1065).

Generating a reply message that includes a selected predefined responseand workout information from a received message allows a user to quicklycompose the reply message that automatically includes the workoutinformation (from the received message) and enables the user to generatethe reply message with minimal user input. Reducing the number of inputsneeded to perform an operation enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

FIG. 10G depicts user interface 1010C displayed on device 1000. Userinterface 1010C includes information identifying a person 1020-1 (e.g.,“John completed a workout!”), selected predefined message 1030-2 (e.g.,“#goals”), and reply message delivery indication 1051 (e.g.,“Delivered”). Reply message delivery indication 1051 indicates thatreply message 1050 (to message 1020) has been sent to external device1090.

FIG. 10H includes user interface 1010A. User interface 1010A includes amessage 1040 (e.g., text message or email) received from an externaldevice. Message 1040 includes workout information. For example, workoutinformation includes information identifying a person 1040-1 (e.g.,“John earned an achievement”), type of workout 1040-2 (e.g., “OutdoorRun”), and achievement sticker 1040-3 indicating a workout achievementwas accomplished by a user (e.g., John) of the external device. In oneembodiment, message 1040 is composed by a workout application on theexternal device, wherein the workout application generates the workoutinformation contained in message 1040. Further, in one embodiment, theworkout application on the external device includes some or all of thefeatures as a workout application, described herein (e.g., workoutapplication as shown in at least FIG. 6A).

User interface 1010A also includes reply affordance 1042-1 (e.g.,configured to enable a user to generate a reply message), muteaffordance 1042-1 (e.g., configured to mute subsequent messages from theexternal device), and dismiss affordance 1042-3 (e.g., configured todismiss message 1020 without sending a reply message).

User input 1015C is received at reply affordance 1042-1 (FIG. 10I).Referring to FIGS. 10J-10K, in response to user input 1015C at replyaffordance 1042-1 and in accordance with a determination that message1040 contains workout information, user interface 1010B is displayed.User interface 1010B is configured to enable a user to compose a replymessage to message 1040. User interface 1010B includes a list ofpredefined responses 1043 corresponding to message 1040 that includesworkout information. Predefined responses 1043 include predefinedresponse 1043-1 (e.g., “you're on fire!”), predefined response 1043-2(e.g., “INCREDIBLE”), predefined response 1043-3 (e.g., “keep it up!”),predefined response 1043-4 (e.g., “you inspire me”), predefined response1043-5 (e.g., “Hello!”), predefined response 1043-6 (e.g., “what'sup?”), predefined response 1043-7 (e.g., “on my way”), and predefinedresponse 1043-8 (e.g., “ok”).

Additionally, user interface 1010B includes affordance 1031 configuredto enable a user to record an audio reply to message 1040, affordance1032 configured to enable a user to select emojis for a reply message tomessage 1040, affordance 1033 configured to enable a user to send ahandwritten reply message (or sticker) to message 1040, and affordance1034 configured to enable a user to send a reply message (that includestext generated from handwriting input) to message 1040.

In one embodiment, in accordance with a determination that message 1040does not contain workout information (e.g., a text that includes “HiJane”), the message is displayed at device 1000. However, predefinedresponses 1043 are not displayed at device 1000.

User input 1015D is received at predefined response 1043-4. In responseto user input 1015D at predefined response 1043-4, a reply message tomessage 1040 is composed (e.g., reply message 1060 in FIG. 10L). In oneembodiment, subsequent to receiving user input 1015D at predefinedresponse 1043-4, an intermediary user interface is displayed thatprompts the user to compose the reply message. In response to user inputto compose the reply message, the reply message to message 1040 iscomposed.

FIGS. 10L-10M depict user interface 1010C (e.g., text message userinterface) displayed at companion device 1065 (e.g., companion device todevice 1000) and external device 1090. Referring to FIG. 10L, replymessage 1060 is displayed at companion device 1065. In one embodiment,reply message 1060 is displayed at device 1000. Reply message 1060includes selected predefined message 1043-4 (e.g., “You inspire me”selected at device 1000, FIG. 10K) and workout information, such asinformation identifying a person 1040-1 (e.g., “John earned anachievement”), and achievement sticker 1040-3. At companion device 1065,reply message 1060 is displayed in-line with other messages (fromexternal device 1090). Referring to FIG. 10M, reply message 1060 isreceived at external device 1090 and displayed at external device 1090.At external device 1090, reply message 1060 is displayed in-line withother messages (from companion device 1065).

FIG. 10N depicts user interface 1010C displayed on device 1000. Userinterface 1010C includes information identifying a person 1040-1 (e.g.,“John earned an achievement”), selected predefined message 1043-4 (e.g.,“you inspire me”), and reply message delivery indication 1051 (e.g.,“Delivered”). Reply message delivery indication 1051 indicates thatreply message 1060 (to message 1020) has been sent to external device1090.

FIG. 11 is a flow diagram illustrating a method for composing a replymessage that includes a selected predefined response, and workoutinformation. Method 1100 is performed at a device (e.g., 100, 300, 500,600, 800, or 1000) with one or more processors, and memory. Someoperations in method 1100 are, optionally, combined, the order of someoperations are, optionally, changed, and some operations are,optionally, omitted.

As described below, method 1100 provides, among other things, anintuitive way for, a user to quickly compose a reply message thatautomatically includes workout information (from the received message)and enables the user to generate the reply message with minimal userinput. The method reduces the cognitive burden on a user byautomatically including, in the reply message, the workout informationfrom the received message. For battery-operated computing devices,enabling a user to select a workout from a list of workouts and launch aphysical activity tracking function faster and more efficientlyconserves power and increases the time between battery charges.

At block 1110, a message (e.g., 1020) is received at the device (e.g.,1000) from an external device (e.g., 1090).

At block 1120, in accordance with a determination that the message(e.g., 1020) contains workout information (e.g., 1020-1, 1020-2, or1020-3), one or more predefined responses (e.g., 1030) to the receivedmessage are displayed.

At block 1130, user input (e.g., 1015B) is received corresponding toselecting a predefined response of the one or more predefined responses(e.g., 1030-2).

At block 1140, subsequent to receiving the user input (e.g., 1015B), areply message (e.g., 1050) is composed, wherein the reply messagecomprises the selected predefined response (e.g., 1030-2) and theworkout information (e.g., 1020-1, 1020-2, or 1020-3).

In some embodiments, the message (e.g., 1020) is displayed at the device(e.g., 1000). In some embodiments, the composed message (e.g., 1050) issent to an external device (e.g., 1090) in response to user input (e.g.,1015B) for selecting a predefined response (e.g., 1030-2). In someembodiments, in accordance with a determination that the message (e.g.,1020) does not contain workout information, the message is displayed(e.g., displayed at device 1000) without subsequently displaying the oneor more predefined responses (e.g., 1030).

In some embodiments, the workout information includes informationidentifying a person (e.g., 1020-1), workout metrics (e.g., 1020-3),type of workout (e.g., 1020-2), or an achievement sticker (e.g.,1040-3).

Note that details of the processes described above with respect tomethod 1100 (e.g., FIG. 11) are also applicable in an analogous mannerto the methods described above. For example, method 1100 optionallyincludes one or more of the characteristics of the various methodsdescribed above with reference to method 700. For example, method 1100includes workout metrics similar to workout metrics described withrespect to method 700. For brevity, these details are not repeatedbelow.

FIGS. 12A-12M illustrate exemplary user interfaces associated with aheart rate tracking application, in accordance with some embodiments.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIG. 13.

FIG. 12A illustrates device 1200 with touch sensitive display 1202.Device 1200 includes various input mechanisms that receives user input,such as, rotatable input mechanism 1203, that is able to receive arotatable input (and may also receive a push input), and input mechanism1204 that is able to receive a push user input. In some embodiments,device 1200 includes some or all of the features of device 100, device300, device 500, device 600, device 800, or device 1000.

Referring to FIGS. 12A-12B, user interface 1210A of a heart rateapplication is displayed on touch sensitive display 1202. User interface1210A includes a list of affordances 1220. List of affordances 1220include affordance 1221 associated with a current heart rate (of theuser of device 1200), affordance 1222 associated with a heart rateduring a physical activity (e.g., outdoor run), and affordance 1223associated with a heart rate during a breathe session of a breatheapplication.

One or more affordances in the list of affordances 1220 identifies aphysical activity associated with the affordance. For example,affordance 1221 identifies activity 1221-1 (e.g., user's activityassociated with current heart rate), affordance 1222 identifies activity1222-1 (e.g., outdoor run), and affordance 1223 identifies activity1223-1 (e.g., breathe session).

One or more affordances in the list of affordances 1220 identifies heartrate information associated with a physical activity. For example,affordance 1221 identifies heart rate information 1221-2 (e.g., 75 BPM,69 resting). Affordance 1222 identifies heart rate information 1222-2(e.g., avg. heart rate 138 BPM), and affordance 1223 identifies heartrate information 1223-2 (e.g., 60 BPM). In one embodiment, the heartrate information is measured by a physical activity tracking sensor ofdevice 1200.

Displaying a list of affordances that identify a physical activity andassociated heart rate information enables a user to quickly view thephysical activity and associated heart rate information and select anaffordance to view additional heart rate information associated with thephysical activity. Reducing the number of inputs to view additionalheart rate information enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

User input 1215A is received at affordance 1220-1 (FIG. 12B). Inresponse to user input 1215A at affordance 1220-1, user interface 1210Bis displayed (FIG. 12C). User interface 1210B includes graph 1230. Graph1230 is a graph of the current heart rate of the user over a period oftime (e.g., today's heart rate). User interface 1210B also includesactivity 1221-1 (e.g., user's activity associated with current heartrate) and heart rate information 1221-2 (e.g., 75 BPM, 69 resting).

Graph 1230 includes physical activity points corresponding to a heartrate of various physical activities. For example, graph 1230 includesphysical activity point 1230-1 that corresponds to the current heartrate, physical activity point 1230-2 that corresponds to the outdoorrun, and physical activity point 1230-3 that corresponds to the breathesession. As shown in FIG. 12C, physical activity point 1230-1 thatcorresponds to the current heart rate is highlighted because the currentheart rate information corresponds to selected affordance 1221.

User input 1215B (e.g., rotational input) is received at rotatable inputmechanism 1203 (FIG. 12D). In response to user input 1215B at rotatableinput mechanism 1203, activity 1222-1 (e.g., outdoor run) andcorresponding metrics (e.g., 142 High BPM, 138 BPM avg.) are displayed(FIG. 12E). Additionally, physical activity point 1230-2 thatcorresponds to the outdoor run is highlighted.

In response to further user input 1215B at rotatable input mechanism1203, activity 1222-3 (e.g., breath session) and corresponding metrics(e.g., 60 BPM) are displayed (FIG. 12F). Additionally, physical activitypoint 1230-3 that corresponds to the breathe session is highlighted.

Referring to FIGS. 12G-12H, user input 1215C is received at affordance1231. In response to user input 1215C at affordance 1231, the previoususer interface 1210A is displayed (FIG. 12H).

User input 1215D is received at affordance 1222 (FIG. 12H). In responseto user input 1215D at affordance 1222, user interface 1210B isdisplayed (FIG. 12I). User interface 1210B includes graph 1240. Graph1240 is a graph of the heart rate of the user during the outdoor runover the duration of the outdoor run. User interface 1210B also includesactivity 1221-2 (e.g., outdoor run) and corresponding metrics (e.g., 142High BPM and 116 BPM avg.). Graph 1240 also includes average heart rate1240-1 (e.g., 116 BPM) over the duration of the outdoor run.

In some embodiments, user input (e.g., tap gesture) is received on touchsensitive display 1202 (FIG. 12I). In response to the user input ontouch sensitive display 1202, user interface 1210B displays graph 1245.Graph 1245 is a graph of the heart rate of the user during a recoveryperiod (or cool down period) after completion of a physical activity(e.g., outdoor run). For example, graph 1245 includes heart rateinformation 1245-1 at a first duration after the outdoor run (e.g., 98BPM at one minute after the outdoor run), heart rate information 1245-2at a second duration after the outdoor run (e.g., 74 BPM at two minutesafter the outdoor run), and heart rate information 1245-3 at a thirdduration after the outdoor run (e.g., 68 BPM at three minutes after theoutdoor run). Additionally, graph 1245 includes a first heart rate point1246-1 that corresponds with the heart rate information 1245-1 (e.g., 98BPM), a second heart rate point 1246-2 that corresponds with heart rateinformation 1245-2 (e.g., 74 BPM), and a third heart rate point 1246-3that corresponds with heart rate information 1245-3 (e.g., 68 BPM).

Referring to FIGS. 12K-12L, user input 1215E is received at affordance1231. In response to user input 1215E at affordance 1231, the previoususer interface 1210A is displayed (FIG. 12L).

User input 1215F is received at affordance 1223 (FIG. 12L). In responseto user input 1215F at affordance 1223, user interface 1210B isdisplayed (FIG. 12M). User interface 1210B includes graph 1250. Graph1250 is a graph of the heart rate of the user during the breathe sessionover the duration of the breath session. User interface 1210B alsoincludes activity 1223-1 (e.g., breathe session) and heart rateinformation 1223-2 (e.g., 60 BPM) associated with the breathe session.Graph 1250 includes average heart rate 1250-1 over the duration of thebreathe session.

FIG. 13 is a flow diagram illustrating a method for displaying ascrollable list of affordances associated with heart rate information.Method 1300 is performed at a device (e.g., 100, 300, 500, 600, 800,1000, or 1200) with one or more processors, and memory. Some operationsin method 1300 are, optionally, combined, the order of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 1300 provides, among other things, anintuitive way for selecting an affordance to view additional heart rateinformation. The method reduces the cognitive burden on a user byenabling a user to quickly view multiple physical activities andassociated heart rate information. For battery-operated computingdevices, enabling a user to view multiple physical activities andassociated heart rate information faster and more efficiently conservespower and increases the time between battery charges.

At block 1310, a scrollable list of affordances (e.g., 1220) associatedwith heart rate information is displayed. The scrollable list ofaffordances includes at least a first affordance (e.g., 1221) and asecond affordance (e.g., 1222). The first affordance (e.g., 1221)identifies a first physical activity (e.g., 1221-1), and a first heartrate information (e.g., 1221-2), wherein the first heart rateinformation is measured by the physical activity tracking sensor. Thesecond affordance (e.g., 1222) identifies a second physical activity(e.g., 1222-1), and a second heart rate information (e.g., 1222-2),wherein the second heart rate information is measured by the physicalactivity tracking sensor. The second heart rate information (e.g.,1222-2) is different than the first heart rate information (e.g.,1221-2).

At block 1320, user input (e.g., 1215A) is received.

At block 1330, in accordance to a determination that the user inputcorresponds to the first affordance (e.g., 1221), additional first heartrate information (e.g., 1230) is displayed.

At block 1340, in accordance to a determination that the user inputcorresponds to the second affordance, additional second heart rateinformation (e.g., 1240) is displayed, wherein the additional secondrate information (e.g., 1240) is different than the additional firstheart rate information (e.g., 1230).

In some embodiments, the additional first heart rate information or theadditional second heart rate information includes a graph of heart rateover time (e.g., 1240), and a graph of average heart rate over the time(e.g., 1240-1), a graph of a breathing heart rate over time (e.g.,1250), a graph of a current heart rate over a predetermined time period(e.g., 1230), a graph of a workout heart rate over time (e.g., 1240), ora graph of a heart rate subsequent completion of a workout over apredetermined period of time (e.g., 1245). In one embodiment, theadditional first heart rate information is concurrently displayed withthe first heart rate information (e.g., 1210B).

Note that details of the processes described above with respect tomethod 1300 (e.g., FIG. 13) are also applicable in an analogous mannerto the methods described below. For example, method 1300 optionallyincludes one or more of the characteristics of the various methodsdescribed below with reference to method 1500. For example, method 1300,in some embodiments, includes displaying a heart rate affordance inaccordance to determining that heart rate data satisfies a heart ratealert criteria. For brevity, these details are not repeated below.

FIGS. 14A-140 illustrates exemplary user interfaces associated with aheart rate tracking application, in accordance with some embodiments.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIG. 15.

FIG. 14A illustrates device 1400 with touch sensitive display 1402.Device 1400 includes various input mechanisms that receives user input,such as, rotatable input mechanism 1403, that is able to receive arotatable input (and may also receive a push input), and input mechanism1404 that is able to receive a push user input. In some embodiments,device 1400 includes some or all of the features of device 100, device300, device 500, device 600, device 800, device 1000, or device 1200.

Referring to FIG. 14A, user interface 1410A is displayed on touchsensitive display 1402. User interface 1410A includes heart rateinformation 1420 (e.g., 75 BPM, 2 min ago). Heart rate information 1420is a current heart rate of the user of device 1400. User interface 1410Aincludes one or more affordances associated with respective applications(e.g., affordance 1421 associated with a workout application, andaffordance 1422 associated with an activity tracking application).Additionally, user interface 1410A includes time, date, temperature,etc.

User input 1415A is received at touch sensitive display 1402corresponding to heart rate information 1420 (FIG. 14B). In response touser input 1415A at touch sensitive display 1402, user interface 1415Bis displayed (FIG. 14C). User interface 1410B, in some embodiments, issimilar to user interface 1210A (FIG. 12A), described above. Userinterface 1410B includes affordance 1421 associated with a current heartrate of the user of device 1400. Affordance 1421 identifies a physicalactivity 1421-1 (e.g., user's current activity associated with currentheart rate), and heart rate information 1421-2 (e.g., 75 BPM measured 2min ago (from current time)).

While tracking heart rate data (e.g., user's current heart rate)corresponding to data received from a physical active tracking sensor ofdevice 1400, it is determined that the heart rate data satisfies a heartrate alert criteria (e.g., tracked heart rate data is arrhythmic). Inresponse to determining that the heart rate data satisfies the heartrate alert criteria (e.g., tracked heart rate data is determined to bearrhythmic), user interface 1410C is displayed (FIG. 14D). Userinterface 1410C includes a heart rate alert affordance 1430 that alertsthe user that the user's tracked heart rate data satisfies a heart ratealert criteria (e.g., “Heart Health, Possible Arrhythmia Detected”).

In one embodiment, the heart rate alert criteria includes a criterionbased on the heart rate exceeding a heart rate threshold. For example,an instantaneous heart rate exceeds a predetermined heart rate threshold(e.g., heart rate is above 100 BPM, or a heart rate that is below 60BPM), wherein the exceeding the predetermined heart rate thresholdindicates arrhythmia. An instantaneous heart rate may be determined bymeasuring the inter-beat-interval between two successive heart rates.The instantaneous heart rate is based on a single interval (betweensuccessive heart beats). The instantaneous heart rate may be convertedto beats per minute, and such instantaneous heart rates can thereforediffer between successive beats (intervals).

In one embodiment, the heart rate alert criteria includes a criterionthat is satisfied when the heart rate pattern matches a heart rate alertpattern. For example, a pattern of the instantaneous heart rate (e.g.,irregular instantaneous heart rate between successive beats) matches aheart rate alert pattern that is indicative of an arrhythmia.

Displaying a heart rate alert icon when it is determined that the user'stracked heart information indicates that the user may have anarrhythmia, promptly alerts the user that they may have a heartcondition that should be diagnosed by a medical professional. Performingan operation when a set of conditions has been met without requiringfurther user input enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

User input 1415B is received at heart rate alert affordance 1430 (FIG.14D). In response to receiving user input 1415B at heart rate alertaffordance 1430, user interface 1410D is displayed (FIG. 14E). Userinterface 1410D provides information directing the user that furtherdetails associated with the heart rate data can be accessed at acompanion device to device 1400.

FIGS. 14F-140 depicts companion device 1490 that is paired to device1400. Companion device 1490 includes touch sensitive display 1491.Companion device 1490, in some embodiments, when paired to device 1400is able to display the application views and perform at least some ofthe same processes as device 1400, as described, herein.

Referring to FIG. 14F, user interface 1492A includes a list ofaffordances 1493 associated with respective applications (e.g., watchapplication, camera application, weather application, clock application,and health application). Affordance 1493-1 is associated with a healthapplication. The health application displays heart rate data, which willbe described in further detail below. Additionally, in some embodiments,the health application on companion device 1490 is configured to controlvarious features and functionality of a corresponding health applicationon device 1400.

User input 1415C is received at affordance 1493-1 associated with thehealth application (FIG. 14G). In response to user input 1415C, userinterface 1492B is displayed (FIG. 14H). User interface 1492B includesvarious affordances 1494 associated with health data. For example, userinterface 1492B includes affordance 1494-1 associated with activitydata, affordance 1494-2 associated with heart health data, affordance1494-3 associated with mindfulness data, affordance 1494-4 associatedwith nutrition data, and affordance 1494-5 associated with sleep data.

User input 1415D is received at affordance 1494-2. User input 1415D isreceived at affordance 1494-2 (FIG. 14I). In response to user input1415D, user interface 1492C is displayed (FIG. 14J). User interface1492C includes graph 1495. Graph 1495 includes the heart rate data thatsatisfies the heart rate alert criteria over a period of time. Forexample, graph 1495 is a tachogram of the heart rate data (thatsatisfies the heart rate alert criteria) over a predetermined period oftime (e.g., 21 seconds). Graph 1495 includes normal heart rate 1495-1over the same time period. Graph 1495 is displayed subsequent receivinguser input 1415B at heart alert affordance 1430 (FIG. 14D).

User interface 1492C includes graph type 1496-1 (e.g., tachogram), heartrate data tracking period 1496-2 (e.g., 21 seconds), additional graphinformation 1496-3, user instructions 1496-4, and heart alert setting1496-5 (e.g., enabled or disabled). In one embodiment, the setting ofheart rate alert setting 1496-5 corresponds to a user-selected settingat device 1490. In another embodiment, the setting of heart rate alertsetting 1496-5 corresponds to a default setting at device 1490.

User interface 1492C includes scrollable heart data affordances 1497-1,1497-2, and 1497-3. The scrollable heart data affordances are associatedwith a set heart rate data corresponding to data received from thephysical activity tracking sensor. The scrollable heart data affordancesidentify the date and time that the heart rate data was received fromthe physical activity tracking sensor. For example, heart dataaffordance 1497-1 identifies the date 1498-1 (e.g., Today, Nov. 16,2016), and time 1498-2 (e.g., 5:21 pm) that the associated data wasreceived from the physical activity tracking sensor.

Graph 1495 corresponds with heart rate data associated with affordance1497-1 (FIG. 14J). Accordingly, affordance 1497-1 is highlighted withrespect to affordances 1497-2 and 1497-3.

Referring to FIGS. 14K-14M, user input 1415E (e.g., swipe gesture) isreceived near scrollable heart data affordances 1497-1, 1497-2, and1497-3. In response to user input 1415E, heart data affordances 1497-1,1497-2, and 1497-3 are scrolled to a new position. For example, theaffordances are translated to the left such that at least affordance1497-3 is fully displayed.

Referring to FIGS. 14N-140, user input 1415F is received at affordance1497-3. In response to user input 1415F received at affordance 1497-3,graph 1495 is replaced by graph 1499 (FIG. 140). Graph 1499 correspondswith heart rate data associated with affordance 1497-3. Accordingly,affordance 1497-3 is highlighted with respect to affordances 1497-1 and1497-2. It should be appreciated that heart rate data associated with atleast one affordance (e.g., affordance 1497-1, 1497-2, or 1497-3) isheart rate data that satisfies the heart rate alert criteria. In someembodiments, heart rate data associated with at least one affordance(e.g., affordance 1497-1, 1497-2, or 1497-3) is heart rate data thatdoes not satisfy the heart rate alert criteria.

It should be appreciated that heart rate data (e.g., heart rate datathat satisfies the heart rate alert criteria) can be transmitted to anexternal device. For example, the heart rate data can be sent (e.g.,email or text) to a device of a medical professional such that themedical professional can access/view the heart rate data.

FIG. 15 is a flow diagram illustrating a method for displaying a heartrate alert affordance. Method 1500 is performed at a device (e.g., 100,300, 500, 600, 800, 1000, 1200, or 1400) with one or more processors,and memory. Some operations in method 1500 are, optionally, combined,the order of some operations are, optionally, changed, and someoperations are, optionally, omitted.

As described below, method 1500 provides, among other things, anintuitive way for promptly alerting a user of a possible heartbeatirregularity. The method reduces the cognitive burden on a user byenabling a user to quickly view a heart rate alert and subsequently viewthe heart rate data that satisfies the heart rate alert criteria. Forbattery-operated computing devices, enabling a user to view heart ratedata that satisfies the heart rate alert criteria faster and moreefficiently conserves power and increases the time between batterycharges.

At block 1510, while tracking heart rate data corresponding to datareceived from the physical activity tracking sensor (e.g., trackingcurrent heart rate data), it is determined whether the heart rate datasatisfies a heart rate alert criteria (e.g., heart rate data matches anirregular heart beat pattern).

At block 1520, in accordance to determining that the heart rate datasatisfies the heart rate alert criteria, a heart rate alert affordanceis displayed (e.g., 1430).

At block 1530, user input (e.g., 1415B) corresponding to the heart ratealert affordance is received.

At block 1540, subsequent to receiving the user input corresponding tothe heart rate alert affordance, a graph (e.g. 1495) comprising theheart rate data that satisfies the heart rate alert criteria over aperiod of time is displayed. At block 1550, in accordance to determiningthat the heart rate data (e.g., user's current heart rate data) does notsatisfy the heart rate alert criteria, forgoing display of the heartrate alert affordance (e.g., 1430 is not displayed).

In some embodiments, the graph 1495 includes expected or normal heartrate over a period of time 1495-1. In some embodiments, the heart ratealert criteria includes a criterion based on the heart rate exceeding aheart rate threshold. In some embodiments, the heart rate alert criteriaincludes a criterion that is satisfied when the heart rate patternmatches a heart rate alert pattern. In some embodiments, the heart ratedata is instantaneous heart beat acceleration. In some embodiments, thegraph 1495 of the heart rate data is a tachogram.

In some embodiments, the heart rate data is transmitted to an externaldevice. For example, the heart rate data is sent to (e.g., email, text)a device of a medical professional.

Note that details of the processes described above with respect tomethod 1500 (e.g., FIG. 15) are also applicable in an analogous mannerto the methods described below. For example, method 1500 optionallyincludes one or more of the characteristics of the various methodsdescribed above with reference to method 700. For example, method 1500,in some embodiments, includes launching a physical activity trackingfunction in response to selection of an affordance in scrollable list ofaffordances. For brevity, these details are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content that maybe of interest to them. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, home addresses,or any other identifying information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables calculatedcontrol of the delivered content. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data will comply withwell-established privacy policies and/or privacy practices. Inparticular, such entities should implement and consistently use privacypolicies and practices that are generally recognized as meeting orexceeding industry or governmental requirements for maintaining personalinformation data private and secure. For example, personal informationfrom users should be collected for legitimate and reasonable uses of theentity and not shared or sold outside of those legitimate uses. Further,such collection should occur only after receiving the informed consentof the users. Additionally, such entities would take any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for targeted content delivery services. Inyet another example, users can select to not provide precise locationinformation, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publically available information.

What is claimed is:
 1. An electronic device, comprising: a display; atouch-sensitive surface; a physical activity tracking sensor; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: displaying a scrollable list of affordancesassociated with heart rate information, the scrollable list ofaffordances comprising: a first affordance identifying: a first physicalactivity, and first heart rate information associated with the firstphysical activity, wherein the first heart rate information is measuredby the physical activity tracking sensor; and a second affordanceidentifying: a second physical activity, and second heart rateinformation associated with the second physical activity, wherein thesecond heart rate information is different than the first heart rateinformation, and wherein the second heart rate information is measuredby the physical activity tracking sensor; receiving user input; inaccordance to a determination that the user input corresponds to thefirst affordance, displaying additional first heart rate information;and in accordance to a determination that the user input corresponds tothe second affordance, displaying additional second heart rateinformation, wherein the additional second heart rate information isdifferent than the additional first heart rate information.
 2. Theelectronic device of claim 1, wherein the additional first heart rateinformation or the additional second heart rate information includes: agraph of heart rate over time; and a graph of average heart rate overthe time.
 3. The electronic device of claim 1, wherein the additionalfirst heart rate information or the additional second heart rateinformation includes: a graph of a breathing heart rate over time. 4.The electronic device of claim 1, wherein the additional first heartrate information or the additional second heart rate informationincludes: a graph of a current heart rate over a predetermined timeperiod.
 5. The electronic device of claim 1, wherein the additionalfirst heart rate information or the additional second heart rateinformation includes: a graph of a workout heart rate over time.
 6. Theelectronic device of claim 1, wherein the additional first heart rateinformation or the additional second heart rate information includes: agraph of a heart rate subsequent completion of a workout over apredetermined period of time.
 7. A method, comprising: at an electronicdevice with a display, a touch-sensitive surface, and a physicalactivity tracking sensor: displaying a scrollable list of affordancesassociated with heart rate information, the scrollable list ofaffordances comprising: a first affordance identifying: a first physicalactivity, and first heart rate information associated with the firstphysical activity, wherein the first heart rate information is measuredby the physical activity tracking sensor; and a second affordanceidentifying: a second physical activity, and second heart rateinformation associated with the second physical activity, wherein thesecond heart rate information is different than the first heart rateinformation, and wherein the second heart rate information is measuredby the physical activity tracking sensor; receiving user input; inaccordance to a determination that the user input corresponds to thefirst affordance, displaying additional first heart rate information;and in accordance to a determination that the user input corresponds tothe second affordance, displaying additional second heart rateinformation, wherein the additional second heart rate information isdifferent than the additional first heart rate information.
 8. Anon-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device with a display, a touch-sensitive surface, and aphysical activity tracking sensor, the one or more programs includinginstructions for: displaying a scrollable list of affordances associatedwith heart rate information, the scrollable list of affordancescomprising: a first affordance identifying: a first physical activity,and first heart rate information associated with the first physicalactivity, wherein the first heart rate information is measured by thephysical activity tracking sensor; and a second affordance identifying:a second physical activity, and second heart rate information associatedwith the second physical activity, wherein the second heart rateinformation is different than the first heart rate information, andwherein the second heart rate information is measured by the physicalactivity tracking sensor; receiving user input; in accordance to adetermination that the user input corresponds to the first affordance,displaying additional first heart rate information; and in accordance toa determination that the user input corresponds to the secondaffordance, displaying additional second heart rate information, whereinthe additional second heart rate information is different than theadditional first heart rate information.